You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we attmept to use the 'close checked items' on our bitnami redmine install, we get a login form shown, but the login does not validate. We are using LDAP and mod_authnz_ldap.so. The environment is a Redmine Bitnami install on Windows Server 2008 with versions as follows:
Environment:
Redmine version 2.3.2.stable
Ruby version 1.9.3-p231 (2012-05-25) [i386-mingw32]
Rails version 3.2.13
Environment production
Database adapter Mysql2
Redmine plugins:
ekanban 0.0.1
redmine_backlogs v1.0.3
redmine_screenshot_paste 2.1.0
All other parts of the site (outside of the eKanBan plugin) are working as expected. We are able to update issue items by dragging and dropping them into a different eKanBan pane, just not close items.
(Note this is the very latest version of the eKanBan plugin, although the version number does not appear to reflect the version number documented on the plugin site of 0.1.1
Has anyone experienced any similar issue?
The text was updated successfully, but these errors were encountered:
When we attmept to use the 'close checked items' on our bitnami redmine install, we get a login form shown, but the login does not validate. We are using LDAP and mod_authnz_ldap.so. The environment is a Redmine Bitnami install on Windows Server 2008 with versions as follows:
Environment:
Redmine version 2.3.2.stable
Ruby version 1.9.3-p231 (2012-05-25) [i386-mingw32]
Rails version 3.2.13
Environment production
Database adapter Mysql2
Redmine plugins:
ekanban 0.0.1
redmine_backlogs v1.0.3
redmine_screenshot_paste 2.1.0
All other parts of the site (outside of the eKanBan plugin) are working as expected. We are able to update issue items by dragging and dropping them into a different eKanBan pane, just not close items.
(Note this is the very latest version of the eKanBan plugin, although the version number does not appear to reflect the version number documented on the plugin site of 0.1.1
Has anyone experienced any similar issue?
The text was updated successfully, but these errors were encountered: