-
Bug
-
Resolution: Duplicate
-
Low (View bug fix roadmap)
-
None
-
6.1.5
-
6.01
-
Steps to reproduce :
- Synchronise your JIRA with LDAP
- Create an UserPicker CustomField CF
- Add user A to LDAP --> User appear in JIRA
- Create an issue and use User A in Customfield CF
- Disable user A in LDAP --> User is deleted into JIRA
It 'll be better to disable it....
No problems with system field like reporter or assignee
- duplicates
-
JRASERVER-24937 When a user is deleted in AD or Crowd, JIRA could keep the user in JIRA as an inactive user
- Closed
- was cloned as
-
JDEV-27024 Failed to load
[JRASERVER-36229] User used in user picker customfield was deleted by crowd
| Minimum Version | New: 6.01 |
| Workflow | Original: JAC Bug Workflow v2 [ 2838417 ] | New: JAC Bug Workflow v3 [ 2924806 ] |
| Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
| Workflow | Original: JIRA Bug Workflow w Kanban v7 - Restricted [ 2568136 ] | New: JAC Bug Workflow v2 [ 2838417 ] |
| Workflow | Original: JIRA Bug Workflow w Kanban v6 - Restricted [ 1533924 ] | New: JIRA Bug Workflow w Kanban v7 - Restricted [ 2568136 ] |
| Labels | Original: warranty | New: affects-server warranty |
| Workflow | Original: JIRA Bug Workflow w Kanban v6 [ 666438 ] | New: JIRA Bug Workflow w Kanban v6 - Restricted [ 1533924 ] |
| Workflow | Original: JIRA Bug Workflow w Kanban v5 [ 642852 ] | New: JIRA Bug Workflow w Kanban v6 [ 666438 ] |
| Workflow | Original: JIRA Bug Workflow w Kanban v5 [ 589972 ] | New: JIRA Bug Workflow w Kanban v6 [ 642852 ] |
| Resolution | New: Duplicate [ 3 ] | |
| Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |