I am trying to create an automation that will update the status based upon status transitions of a linked issue in another project. The trick here is that I want to compare the statuscategory of the trigger issue to the status category of linked issues. The reason for this is that trigger issue workflow has many different statues for each statuscategory whereas the linked issue status is simply To Do > In progress > Done.
So basically...
trigger - Issue transitioned
conditions - unimportant here but several exist
branch - linked issues
condition - compare trigger issue statuscategory to linked issue statuscategory
If trigger statuscategory = In Progress but linked issue does not then transition linked issue to "In Progress"
Else if trigger statuscategory = Done but linked issue does not then transition linked issue to Done
Note: I considered simply using "Status" but rule maintainability becomes an issue if statuses change.
Update...
I think I have figured out the key piece using the below rule as a test. I am opting to use log action rather than actual transition actions during my early testing to keep things simple.
One odd observance here. During my testing I transitioned an issue from In Progress back to To Do status. I would have expected to see in my log action a value of "To Do" however, I saw "New". I don't ever recall seeing new as a statuscategory.
In any event I am moving on to see if I can formulate the entire rule as I need it. I will update here if and when I get it all working.
New is a frequent status I see on a lot of sights that users add. It could be used somewhere but if your using statusCategory are you calling which statusCategory you want to transition too?
The action for the last step would or should be transition issue of linked issue into StatusCategory Done correct? How would the issue get transitioned to To Do if you are calling out the transition. Unless you are not calling a specific transition?
In the past when doing these types of automations I typically will call out a specific link type so that it is the trigger each time and found that its helpful.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You might want to handle the To Do status specifically if it is returning something other than a To Do statusCategory.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes "New" is what is being returned as a status category which I have not seen before. I am going to try to understand this further
example...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I think you should open a support ticket and have Atlassian answer that. I think you have stumbled upon a new secret.
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.