-
Bug
-
Resolution: Duplicate
-
Low
-
None
-
6.3.6
-
6.03
-
When there is another field in an issue that is an invalid state, quick edit fails complaining that the user is not assignable.
This is fails, the user is assignable, and the real failure is different.
My case: I have a select one which was None and but didn't allow None as a value.
Please fix this as our users are raising tickets regarding broken configuration when in fact, is JIRA that is displaying the wrong messages.
If the user would use the Edit screen, they would be able to see the real error, but obviously they do not know this.
- blocks
-
JRASERVER-69289 Password is not correctly set when deploying Jira Data Center on Azure
- Closed
- duplicates
-
JRASERVER-40124 Assignable Users are no longer assignable for an issue if they don't belong to the Issue Security Level permissions
- Closed
- is related to
-
JRASERVER-38134 Warn when/prevent from, assigning issue to user who does not have appropriate security level
- Gathering Interest