-
Bug
-
Resolution: Fixed
-
High
-
None
-
43
-
Minor
-
26
-
Issue Summary
If a project has a default assignee but the default assignee does not have the assignable user permission, when creating a subtask through the new issue view, users would be prompted a generic error message stating that
We couldn't create the subtask
Check your connection, then give it another try
Steps to Reproduce
- Set default assignee on Project Settings details tab
- Make sure default assignee does not have the assignable user permission
- Go to any task and make sure you're in the new issue view
- Create sub task
Expected Results
Just like the old view, error message that states "The default assignee does NOT have ASSIGNABLE permission OR Unassigned issues are turned off."
Actual Results
Generic error message is prompted
Workaround
Create sub task in the old view to see the error message or run the developer console to see the error. The error message is visible in Console log:
{"errorMessages":[],"errors":{"assignee":"The default assignee does NOT have ASSIGNABLE permission OR Unassigned issues are turned off."}}
- is related to
-
-
- Closed
-
- is resolved by
-
BENTO-5630 Failed to load
- mentioned in
-
Page Failed to load
-
Page Failed to load
-
Page Failed to load
-
Page Loading...
-
-
-
-
- relates to
-
[JRACLOUD-73555] Generic error message in the new view when creating a sub task
Hi everyone, thanks for your patience on this, we released a fix for improving create inline error message and it should be available for everyone now. If you still experience the error/issue after that, please comment here to let us know the specific case. Thanks Atlassian engineering.
This also happens when cloning an issue. If there are required fields that were implemented after the issue was created, then you have an issue that doesn't meet the requirements of the Create Issue workflow post-function. In New View it says "We couldn't clone ISSUE-123. Check your connection and then try again". In Old View you get the full error message, in this case for me it was that there was a required second level cascading select that was required, and the error was "Can't clone this issue. Error occurred while creating issue through workflow: Both levels of <field name> should be selected" (the last sentence is a custom error message).
Hi,
I still cannot create sub-tasks and the error has also changed: "We couldn't create the subtask. Field "summary" cannot be set. It is not on the appropriate screen, or unknown.". I've never seen this before.