I've added the auto transition listener in order to reopen an issue if someone sends in an email relating to that issue after it's been closed.
The problem is that we use many different workflows, so the action ID varies depending on the type of issue - in other words, "Reopen" is a transition in most of our workflows, but it has a different ID in each. Because of this, I can't set up the auto transition listener properly because it's looking for a single action ID.
How can I solve this problem?
You can use a global transition for 'Reopen'.
Or else, I can suggest you these two steps.
Thanks for the quick response.
A global transition is "global" only for a single workflow, right? It's not like I can set up one and it works across all of the workflows, correct? So it sounds like I'd need to set up one global transition per workflow.
On the other hand, if I can just go in and edit all of the workflow XML and assign my own ID to Reopen, that should solve it. Are there any potential problems with me doing that? That ID was assigned by JIRA, so I'm a little hesitant about going in there and just changing it however I feel...
Oops... sorry. My understanding of global transitions was wrong.
Please take whatever I've written below 'Or else...' as the answer. :)
I just went through a workflow XML where a common action is used. It shouldn't be a problem to change the action ID, but you have to change it everywhere.
Here's how common action should begin,
<common-actions> <action id="500" name="Reopen" view="fieldscreen">
And here's how it should be reused.
<common-action id="500" />
What you shouldn't mess with is step IDs.
Changing transition IDs should be OK. But don't overuse it. Do it only when required. If you have workflow-related plugins like Behaviours installed, changing some transition IDs may affect the plugin's functionality.
Regarding step IDs, each step ID represents a Status (global) in JIRA. Therefore I don't think it's a good idea to change step IDs. In your case you don't need to mess with them. :)
Be sure to take a backup of your workflow before performing any sort of modification to it.
And don't be scared to modify workflow XML. :) :)
Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...
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