You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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:
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:
(the same error happens for all issue types I can select)
And the error:
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?