The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi, I'm using Jira Software. Whenever I try converting subtask to an issue, I gen a non-descriptive "500 - internal server error".
I'm the project admin and I should have all the permissions. This happens across multiple different subtasks.
Can anyone suggest what should I check for?
Hello @Szymon Sobczak
Welcome to Atlassian Community!
Per your description, I understand you are facing an error when you click in "Move" and try to convert your sub-tasks to issues. Is that correct?
Can you please confirm if the sub-tasks you are facing this problem are in a Next-gen project?
Investigating a little further, I found the following bug reported about your error, reproducible only in a Next-gen project:
- Converting a Sub-task of a Next-gen project to issue results in error 500
If you are using a Next-gen project, please check if the following workaround works for you:
1 - Navigate to your project > Project settings > Issue types > Enable the Story Issue type
2 - Navigate to your sub-task > Convert it to a Story issue type. You will face the same error, however, the sub-task will be properly converted
3 - Change the story to the issue type you want
In case you are not in a next-gen project, please provide us with a screenshot of how you are trying to convert your issues with the generic error you are receiving.
Hi, it's been a while and I've stumbled upon this bug again.
Last time I just manually deleted all the subtasks and created new issues, but this messes up the reports.
I'm not using a next-gen project, this is in a classic one.
This is what I'm doing:
Step 2:
(the same error happens for all issue types I can select)
And the error:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi everyone,
May be an update on this one ?
We're getting the same error, It also happen trying to convert between Standard issue types.
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.
Hello, we've also discovered this bug.
Im curious to know if anyone else sees the permission showing as granted via their permission checker? We do, but the group condition fails (the overall status for the permission is granted).
Is it possible the group condition is causing a bug that interferes with this operation?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I too am getting this bug. It's an old project and I'm not an admin on it, but admins seem to be able to do it for me (convert to an issue)!
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.
👋 Hi there Jira Community! A few months ago we shared with you plans around renaming epics in your company-managed projects. As part of these changes, we highlighted upcoming changes to epics on...
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.