-
Bug
-
Resolution: Unresolved
-
Medium (View bug fix roadmap)
-
None
-
6.4.4, 7.1.2
-
6.04
-
7
-
Severity 2 - Major
-
2
-
Steps to reproduce
- create a group ldap-group in LDAP
- connect JIRA to LDAP using Connector type and sync the directory
- add ldap-group to a permission in a permission scheme
- in LDAP, rename the group to ldap-group-renamed
- sync the directory in JIRA
Expected behavior
In the permission scheme, ldap-group should become ldap-group-renamed
Actual behavior
ldap-group remains the same in the permission scheme
Notes
- ldap-group doesn't exist as an Internal (local) group (only in LDAP)
- this might affect other places where ldap-group can be used e.g. Issue Security Scheme, Global Permissions, Filter Shares, etc.
- duplicates
-
JRASERVER-1391 Provide the ability to rename groups after creation
- Under Consideration
- is caused by
-
-
- Closed
-
Renamed LDAP Group is Not Reflected in Permission Scheme
-
-
Resolution: Unresolved
-
Medium
-
None
-
6.4.4, 7.1.2
-
6.04
-
7
-
Severity 2 - Major
-
2
-
Steps to reproduce
- create a group ldap-group in LDAP
- connect JIRA to LDAP using Connector type and sync the directory
- add ldap-group to a permission in a permission scheme
- in LDAP, rename the group to ldap-group-renamed
- sync the directory in JIRA
Expected behavior
In the permission scheme, ldap-group should become ldap-group-renamed
Actual behavior
ldap-group remains the same in the permission scheme
Notes
- ldap-group doesn't exist as an Internal (local) group (only in LDAP)
- this might affect other places where ldap-group can be used e.g. Issue Security Scheme, Global Permissions, Filter Shares, etc.
- duplicates
-
- Under Consideration
- is caused by
-
-
- Closed
-
-
Unassigned
-
Andy Nguyen (Inactive)
- Votes:
-
16 Vote for this issue
- Watchers:
-
18 Start watching this issue
- Created:
- Updated: