I have configured the Triage requests sent by email automation within my JSD to search for requests containing text and move them to a separate request type. This request type however is attached to a different issue type.
When the email is received by JIRA it is correctly triaged to the new request type however the workflow transitions shown are from a separate part of the workflow. For e.g. the first transition that should be shown to a service desk agent is "Start/Continue" yet it appears as "Review Complete" which is not a valid transition within the NEW status. As such a workflow error is produced:
I am unable to find any similar situations when using google and I'm not sure where to go from here. Has anyone experience similar problems when the issue type is changed through this automation?
There are no workflow conditions or validators that would be causing the transition to not appear.
JIRA Service desk version 3.1.2
JIRA system administrator
Take a look at the text view of the workflows. From there you'll see the ID numbers for the steps and transitions in the source and destination workflows.
I suspect JIRA is just migrating the request type and matching the step and transition ids in the workflow.
Its difficult to know without being able to see your system.
This definitely seems to be the case. The "Start" transition ID shares the same as the "review complete" transition in the new workflow that these emails are to be triaged to.
Is there a way of being able to fix this? is it a possible bug? or am I out of luck?
Its possibly a bug. I would raise it with Atlassian support.
You may be able to work around it. Have you tried moving the issue? With Move you can move the issue to the same project but change the issue type. JIRA will take you through a process of migrating the workflow statuses and transitions. If this works, you can then change the request type.
Yeah I know the move issue process well. Unfortunately we get a lot of automated email notifications which require members of the service desk team to do a lot of manual triaging and this automation was attempting to stop the need for that. I'll log it with Atlassian and see how it goes. Thank you for your help!
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs