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
When attempting to create a subtask, the user is getting the "we couldn't create the subtask Error Server Response: 500.
I logged in as the user and get the same thing. When I try, I also get the same thing. If i try and make a subtask on a different ticket, it works. Any ideas what is going on here?
I have not seen this in this exact situation, however I have a couple idea's.
1. Could be another AWS problem, and it should be resolved in a couple hours to tomorrow. However currently Atlassian Status is all green as of this moment.
2. Try on another project, then try using a different subtask type. It could be a corrupted workflow or automation causing the errors.
3. Go home early, enjoy your day and try again tomorrow.
Is Sub-task a valid Issue Type for this project?
If you have correct definition in issuetype schema, maybe you have temporary connectivity issues (network micro-cuts).
I agreed with other community leaders suggestions.
Again, if your have subtask issue type configured properly for your Jira/JSM project, then it could just be a temporary network issues took place and should be resolved shortly by Atlassian.
However, if the issue continues, then you should contact Atlassian Support (https://support.atlassian.com) for further assistance, so they can access the backend system logs to determine the root cause (not temporary outage) to assist you.
Hope this helps
Best, Joseph Chung Yin
Jira/JSM Functional Lead, Global Technology Applications Team