-
Bug
-
Resolution: Unresolved
-
Low (View bug fix roadmap)
-
None
-
8.20.0
-
8.2
-
3
-
Severity 3 - Minor
-
1
-
Issue Summary
When committing changes, like a new issue, the interface doesn't give any means for the user to know why it failed.
While in the interface the very generic error "Could not be committed for unknown reasons" is thrown, the logs have the error.
Steps to Reproduce
Example of trying to set an invalid assignee:
- Set a project administrator as the default assignee
- Set the project administrator user as inactive
- Create an issue in Advanced Roadmaps
- Attempt to commit the changes
Expected Results
An error that the user can take action on.
Actual Results
The user gets this error:
Item could not be committed for unknown reasons. Please contact your administrator.
The below exception is thrown in the atlassian-jira.log file:
/rest/jpo/1.0/issues/commit [c.a.r.j.c.scenario.issue.IssueScenarioEntityCommitExceptionHandler] Exception when trying to commit issue: Specific error details: {assignee=The default assignee does NOT have ASSIGNABLE permission OR Unassigned issues are turned off.}.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available.
- is related to
-
-
- Closed
-
- relates to
-
-
- Gathering Impact
-
- links to
- mentioned in
-
Page Failed to load
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSWSERVER-24902] When commiting an issue has an error, no details are shown on the interface
Dear all,
I would like to inform you that this issue in the project JPOSERVER is being migrated to the new project JSWSERVER. Your votes and comments will remain unchanged.
Our team at Atlassian will continue to monitor this issue for further updates, so please feel free to share your thoughts or feedback in the comments.
Sincerely,
Aakrity Tibrewal
Jira DC
Hi Team,
Any updates on the issue or any workaround.
Regards,
shiva
I'm experiencing the same issue. Is it possible that required fields that aren't viewable in Roadmaps aren't being populated on creation, and causing the error?
+1, occurs i.e. when users are facing bug
JSWSERVER-24900- some note about the error would make it more clear for user (i.e. for purpose of raising support request for Jira Admins)