Hi Community!
When trying to create a subtask, Jira shows the following errors. Are you getting these too?
* When creating a subtask directly from the main task, it shows: "We couldn't create the subtask. Error server response: 500"
* When creating a subtask going to a filter, clicking on the ellipsis, and selecting the "create subtask" option, it shows: "Couldn't create the issue. We're having some trouble creating the issue. Refresh the page and try again".
However, after refreshing the page, it still doesn't work.
See images attached.
Thank you!
Interesting - we are intermittently seeing what has been described above as well... Either the 'create task' screen gets fired and you can create the ticket as normal.. or the create screen doesn't show and instead we get a 'couldn't create' because (in our case) the 'description' field is mandatory (not unreasonably!).
So it's not throwing a 500 error, but it's intermittently not doing what we would expect...
Hi @Lizzeth Campos and welcome to the Community!
I don't see any images attached. But apart from that, the error message you refer to is not very informative indeed.
Most commonly, failure to create issues is often linked to required fields not being present where you are trying to create the issue. e.g. when you are trying to do this inline from a task, you only have the summary field available. If you have set the description or additional fields as required (for your sub-tasks), Jira says no.
So, check your field configuration or any workflow validators that may require you to fill out fields that you don't see when you are trying to create your sub-tasks and get rid of them. Hopefully that is what is happening here.
Hope this helps!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Walter Buggenhout Thank you! I'll check the field configuration. For now, see the images attached, corresponding to the original message.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
There's nothing conclusive on the screenshots, @Lizzeth Campos. The only things I can see, is that this is a custom made sub-task issue type and that it apparently has a lot of fields on it (I notice there are several tabs on the issue create screen). In the first screenshot, you can see the scenario I was describing. The other scenario is different, but it does happen that a required field is simply not on the screen create screen at all. So, the hypothesis that there may be a required field missing still stands, although I can't tell you which one it might be.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Walter Buggenhout Thank you :) we did a clean-up in our custom fields, and we deleted one that was being used in a post function of that workflow. We weren't using the field in our screens, but we had it in a workflow. After deleting that post function, it worked again. Thankfully we didn't need that post function anymore.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.