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

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Why does the global automation rule change the assignee?

I'll be succinct, I have automation rules for both projects and global.

For Projects, I have rule created every day and assigned to me - but due to the trigger being a schedule (I.e. every 1 day) - I'm unable to perform a transition within the same rule.

For Global, I have one rule that transitions the automatically created Jira tickets to the 'In Progress' status.

Problem is that when the global rule runs - it changes the Assignee, despite this not being a condition/instruction of the rule-set.

See below:


4 answers

Further note, have tested this with the Project specific rules, by turning the global one off - the issues created within the projects stay at the specified assignee.

Not sure if this is part of how global rules are intended or if this is a bug; could probably work-around this by setting a transition rule for each project or further conditions on the global - but wanted to see if others are having this same experience.

0 votes
John Funk Community Leader Oct 12, 2020

Hi @Diskonekted  - Not sure I completely follow what you are asking, but let me see if I can help. 

First, when you say that you cannot transition issues because it uses the Scheduled trigger, I don't think that is a limitation as I perform that functionality with some of my rules. What error are you getting or how is it not working? 

On the second part, since the transition is successfully happening (and it isn't in the Scheduled trigger) there must be a post function in the workflow on the transition to In Progress that assigns the issue. There is no separate functionality that would fire in Automation to assign a user based on whether it is a Project or Global rule. You should check the post functions in the workflow. 

Hi @John Funk ,

Apologies for not being clear - I can perform the transition within the one rule, but it requires me to use some JQL, which I don't want to do right now. So instead I've opted for the two rules.

Regarding the post function; there are none. When the rule setup is like below the assignee is retained:

Project 1 - Rule 1: Every day create task for Joe Bloggs.
Project 1 - Rule 2: Transition automatically created rules to 'In Progress'

But when the below setup occurs, the assignee changes:

Project 1 - Rule 1: Every day create task for Joe Bloggs.

Global - Rule 1: Transition automatically created rules to 'In Progress'.

* All tasks are now assigned to 'Automation for Jira'.

Again, suspect this might be a bug - but grateful if others can test this setup to see if it's common across other subscriptions (my Jira cloud instance is default out-of-the-box).

For completeness & visibility for others who have the same experience, I worked-around the issue by adding in a new action to the end of the global rule. See below:


Still, would be good to understand why this was occurring in the first place.

John Funk Community Leader Oct 13, 2020

I don't see any reason why it would be reassigning unless there is a post function or some other automation rule. Does the reassignment show in the History for the card? (It should) and who does it say is changing the Assignee?

@John Funk , it does show in the Activity - History section of the card. Interestingly the reassignment happens before the transition action - so almost by having the rule start execution it performs the reassignment.

As per the above screenshot, the rule then reassigns to me.


John Funk Community Leader Oct 13, 2020

I would say you have another rule running somewhere that does that. 

@John Funk  where would be the place to confirm this?

I've looked in the Automation Rules Audit Log and this is the only rule which has that Task as the Associated Event.


Additionally, it would be good for someone else to test this setup.

As noted above, I can:

  • Switch off this rule and the original assignee is retained.
  • Copy the rule and make it project specific, the original assignee is retained.

Many thanks to you all.

John Funk Community Leader Oct 14, 2020

Maybe @Simeon Ross can shed some light. He is a good light shedder.  :-)

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Marketplace Apps & Integrations

5 mobile apps for Jira Cloud to boost productivity

  It’s very important to have access to the workflow process from anywhere. Especially if you manage the work of others. There is no difference whether you’re out of office, or drive a ca...

209 views 2 5
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you