Details
-
Bug
-
Resolution: Cannot Reproduce
-
Low
-
3
-
Severity 3 - Minor
-
Description
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? 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.
Attachments
Issue Links
- is related to
-
JRASERVER-14836 Ensure JIRA behaves correctly when a user who has assigned or reported issues has been deleted
- Gathering Interest
- relates to
-
CSMO-460 Loading...