-
Suggestion
-
Resolution: Won't Fix
-
None
-
None
-
None
-
1
-
4
-
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
Jira Software version: v7.2.6#72008
Steps to reproduce:
- In Jira Software, navigate to: Administration -> User management -> User Directories
- Add Directory -> LDAP
- In the "Configure LDAP User Directory" page, expand the Directory Type
Notice that "FedoraDS" is listed as an option. This should be renamed to "389 Directory Server" or "389DS", if there is a character limit. This is because the project was renamed in 2009: http://directory.fedoraproject.org/docs/389ds/FAQ/history.html
- relates to
-
JRACLOUD-63505 FedoraDS in "Configure LDAP User Directory" should be renamed to 389 Directory Server
- Closed
[JRASERVER-63505] FedoraDS in "Configure LDAP User Directory" should be renamed to 389 Directory Server
Resolution | New: Won't Fix [ 2 ] | |
Status | Original: Gathering Interest [ 11772 ] | New: Closed [ 6 ] |
Workflow | Original: JAC Suggestion Workflow [ 3052563 ] | New: JAC Suggestion Workflow 3 [ 3678946 ] |
UIS | New: 1 |
Support reference count | Original: 3 | New: 4 |
Workflow | Original: Confluence Workflow - Public Facing v4 [ 2615980 ] | New: JAC Suggestion Workflow [ 3052563 ] |
Workflow | Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2583041 ] | New: Confluence Workflow - Public Facing v4 [ 2615980 ] |
Status | Original: Open [ 1 ] | New: Gathering Interest [ 11772 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2359656 ] | New: JIRA PM Feature Request Workflow v2 - TEMP [ 2583041 ] |
Support reference count | New: 3 |
Workflow | Original: JIRA Bug Workflow w Kanban v6 [ 2127123 ] | New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2359656 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2089771 ] | New: JIRA Bug Workflow w Kanban v6 [ 2127123 ] |