Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Automation to transition status when assignee has been added

Pineapple November 29, 2024

Hi, 

I would like it if we could automatically transition the status when an assignee has been set from Unassigned. 

For example, 
When the status is in Open, and I were to assign the issue to my team, the status will transition to work in progress. 

I have tried to trigger the automation when an Issue assigned into an
If block that checks if the Status = Open and the initiator is not Automation for Jira
Then it will transition from Open to Work in progress

The issue successfully transition to work in progress but the Assignee becomes "Automation for Jira". Is there any other way to do this where the Assignee will not be reassigned to "Automation for Jira"? 

Thanks for the help

2 answers

1 accepted

5 votes
Answer accepted
Jehan Bhathena
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
November 29, 2024

Hi @Pineapple ,

Can you share a snapshot of the "Transition Issue" action from your automation?

I tested a similar setup at my end and it works:image.png

I'm suspicious that the A4J assignee is being set by :

  • Another automation
  • Post action in a workflow
  • Transition Issue Action has the "Assignee" update field checked or added in the "Additional fields"

Let us know how it goes.

 

Pineapple November 30, 2024

Hi @Jehan Bhathena

Thank you so much for your help!

I completely forgot about my workflow post-action. Once I removed that, the automation started working perfectly!

Like Marc - Devoteam likes this
0 votes
Jack Brickey
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
November 29, 2024

Hi @Pineapple , so the following should work. I would like to see your history on the issue to understand why the issue is being assigned to A4J. That seems very odd.

IMG_4889.jpeg

Pineapple November 29, 2024

Hi @Jack Brickey 

Thanks for your prompt reply!

I updated my rule to match your screenshot but I am still getting A4J being assigned as the assignee.

image.png

Jack Brickey
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
November 30, 2024

Hi @Pineapple , do you have other automation rules active? One possibility, as Jehan mentioned, is another rule is setting the assignee to A4J. If you look at the history the last action is an A4J rule is setting the assignee overwriting your initial assignment. I would definitely check all currently active rules including global rules. Note: it would be an odd use case to set the assignee to A4J. If you do not see another rule setting the assignee to A4J, please share a screenshot of you complete rule. It would also be interesting to add a log action as the last component of your rule to log the assignee at rule exit - "assignee = {{issue.assignee}}".

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events