[JRASERVER-36229] User used in user picker customfield was deleted by crowd - Create and track feature requests for Atlassian products.

XML

Word

Printable

Details

Type: Bug
Status: Closed (View Workflow)
Priority: Low
Resolution: Duplicate
Affects Version/s: 6.1.5
Fix Version/s: None
Component/s: User Management - LDAP Integration, User Management - Others
Labels:
- affects-server
- warranty

Introduced in Version:
6.01
Bug Fix Policy:
View Atlassian Server bug fix policy

Description

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

Attachments

Issue Links

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 Loading...

Activity

People

Assignee:: Unassigned

Reporter:: Frédéric Cilia

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Dates

Created:: 17/Dec/2013 6:29 PM

Updated:: 28/Mar/2019 12:12 AM

Resolved:: 21/Jan/2014 5:05 AM