subtask error

[Clare Lawson]

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?

[Chris Thomas]

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.

[Clare Lawson]

Nothing worked!  I even cloned it and it still didn't work. So, I made a new ticket, and deleted the old one. Must have been a bug of some sort.  Thanks all!

[Michael Thompson]

Is Sub-task a valid Issue Type for this project?

[Clare Lawson]

Yes.

[Marcos Milanesio]

If you have correct definition in issuetype schema, maybe you have temporary connectivity issues (network micro-cuts).

[Joseph Chung Yin]

@Clare Lawson -

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

Viasat Inc.