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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,457,469
Community Members
 
Community Events
176
Community Groups

Jira automation gets assigned to tickets which dilutes tickets ownership

Hi, 

I have a Jira automation role to automatically transition project tickets from state to different state depending on github status. For example, when pull request is created -> put the ticket to onReview 

The functionality works correctly but the problem is that tickets get assigned to `Jira Automation` user as they move, which overrides the assignee and dilutes ticket ownership as all tickets eventually lost its owner as it moves between columns.

I read in this Actor article

It either has to be either a Jira Automation user or a specific user! How can I preserve the ticket assignee as it moves between states? Thank you!

1 comment

First, check the automation to make sure it's not changing the assignee to itself when it makes the transition.  

I'm not familiar with the pull request trigger for Automation, but you should be able to edit the issue to have the assignee be the person that triggered the rule as part of that rule.

Another possibility is that your workflow (or another automation) may be setting the assignee as part of that transition.

Like Yvan Martin likes this

Comment

Log in or Sign up to comment