-
Bug
-
Resolution: Cannot Reproduce
-
Medium
-
25
-
Severity 3 - Minor
-
0
-
NOTE: This bug report is for JIRA Cloud. Using JIRA Server? See the corresponding bug report.
Summary
Attempting to edit an issue when the username is mixed-case and disabled is not possible as it displays the following errors:
- If they're the assignee: User cannot be assigned issues.
- If they're the reporter: The reporter specified is not a user.
Steps to Reproduce
- Create a user with mixed-case username (e.g.: AquaMan).
- Create an issue and assign that user to it, and make them the reporter.
- Deactivate that user.
- Attempt to edit the issue.
Expected Results
The issue is able to be saved.
Actual Results
When saving the issue, the errors in the attached screenshot are presented and the issue cannot be saved.
Workaround
This validation is not applied when using Inline Edit, so it's still possible to edit those fields in the issue. Alternatively, the user could be renamed to lower-case.
Removing the field from the Edit Screen is also a viable workaround.
Notes
This happens for users in the JIRA Internal and Active Directory.
- is duplicated by
-
-
- Closed
-
- is related to
-
-
- Closed
-
[JRACLOUD-38412] Unable to edit an issue when the user is deactivated
This is a compliance problem for many changing the integrity of the data.
I just found out in our setup it's not possible to edit a Resolution of a ticket, assigned to an inactive user
The workaround does not work for fields that do not have a value like Sprint or related Issue! You are forced to click edit.
Sharon Connell
added a comment - I see this behavior for all issues associated with deactivated users. All of the usernames are lowercase. Does this still apply? I cannot search by inactive users and it is skewing reporting.
Sharon Connell
added a comment - I see this behavior for all issues associated with deactivated users. All of the usernames are lowercase. Does this still apply? I cannot search by inactive users and it is skewing reporting. 
Hesky Ji
added a comment - Nearly 3.5 years... This looks as bad as the new logo It seems that there is no workaround when you want to modify time tracking information (original estimate for example), when the issue isn't included in the backlog yet. So it's problematic for our organization.
We also find this problematic, particularly from a record integrity and audibility perspective. From our process perspective, the reporter really should be immutable, but today we simply manage that through our procedures and permissions. Having a scenario where a reporter change is required by JIRA to accomplish further work could raise questions in an audit, though the questions should be answered via the History view.
I have the same issue and in my case, the usernames are all lowercase with dot (firstname.lastname).
The users in question are deactivated but still in the project team group, so they are even assignable according to permissions.
Also, when I activate a user (even without assigning a license), editing works just fine. When I deactivate the user again, I get the "The reporter specified is not a user." error message.
This is on cloud, JIRA v1000.499.3.
+1