Loading...

XML

Word

Printable

UIS:
3
Support reference count:
8
Feedback Policy:

We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

When internal JIRA user management is used, JIRA does not allow users to be deleted if they have reported issues or have issues assigned to them.

Due to this, some sub-systems in JIRA expect that if a user is an assignee or a reporter of an issue, then the user must exist.

This is much harder to enforce when external user management is used. For example, Crowd.

Therefore, JIRA needs to be changed to relax this constraint.

Issues:

Inconsistent Stats - In Browse project, issues under the unassigned bucket may show wrong results. This is due to the null value being mapped to the non-existent user instead of unassigned.
Editing an issue where it is assigned to non-existent user will blow every time the issue is edited.

is duplicated by

JRASERVER-23424 Jira does not handle deleted users wih assigned issues

JRASERVER-15100 Deleting user from Crowd produces stack-traces for ex-user's issues & filters in Jira

is related to

JRASERVER-13685 JIRA should better handle errors return from Crowd (notificaton messages)

JRASERVER-13693 Missing user does bad things on issue update

JRASERVER-15098 Watches and Votes cannot handle users "disappearing" (ie being deleted from external user management).

relates to

JRASERVER-15430 The User Custom Field should handle users being deleted.

JRACLOUD-14836 Ensure JIRA behaves correctly when a user who has assigned or reported issues has been deleted

(2 relates to)