Starting on 3/20 we are getting an error of "We can't perform this action due to invalid data in this issue's workflow. Contact your admin to learn more." when creating issues for any of our projects.
Nothing has changed with our workflows for several years.
Found out this is a known issue, but I was able to resolve after a suggestion by the help desk to remove the post function to HipChat that was in our workflows.
Awesome to hear. Thanks for sharing the findings with the community.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We're suddenly having the same problem just now, on a workflow that hasn't changed in ages. I'm not even sure where to start to "fix" it since it wasn't broken before. This sounds a lot more like a Jira internal issue than a problem with our workflows -- esp. considering that it started happening to multiple customers all at about the same time.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
For the record, we do not have a post to Hip Chat in our workflow.
Update -- well, we did have a HIP Chat post function that we didn't realize was buried in there. We deleted it, and now everything is working again.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Probably pursue similar approach by reviewing the post-function. Might be something no longer compatible like the hip chat.
Definitely, would be a process of elimination to identify what is the root cause.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Brad Collister _Administrator_ ,
It could be a process of elimination to figure which part of the workflow could be an issue. One thing to try is to copy that workflow or recreate the same one and replace the workflow in question.
At the same time, Would raise a ticket with Atlassian to see what they can find from their cloud logs that can help identify the root cause.
Hope this helps.
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.