Hi Fellow-Atlassians,
I'm getting an error " We couldn't create the subtask Error server response 500"
while trying to create a subtask issue.
The summary field is available on the subtask screen definition.
The "Unassigned" user is currently set.
What could be the cause and which setting should I reconfigure to resolve?
Thank you for your insights!
Hi @Ward Schwillens_ Schwillie
Do any other of your colleagues have the same issue?
Can you check the workflow of the subtask and see if any validator or PF exist?
Hi @Alex Koxaras _Relational_ you pointed me in the right direction.
I'm in the process of migrating from server to cloud and my workflow contained some post functions that will not work in cloud.
So I removed these post-functions and it works now.
Thanks, good pass!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Join us to learn how your team can stay fully engaged in meetings without worrying about writing everything down. Dive into Loom's newest feature, Loom AI for meetings, which automatically takes notes and tracks action items.
Register today!Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.