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,362,537
Community Members
 
Community Events
168
Community Groups

Automation not working

We created an automation rule to assign the task to the developer when moved to "ready to release" status. This rule used to work before. But now it does not work properly. 

First, it assigns the issue to the developer. But a moment later, it automatically converts back to "unassigned". How can we fix this?

Ekran Resmi 2022-08-22 15.55.57.png

 

1 answer

1 accepted

2 votes
Answer accepted
Dirk Ronsmans Community Leader Aug 22, 2022

Hey @ozgeseckin ,

In the history of the issue can you see who changed it back to "unassigned" (so cleared the value)? 

I agree with @Dirk Ronsmans

Start with looking at a sample ticket that you are noticing this happening on, and look at the ticket history. From there, you can see if it's someone doing it manually or if it's an automation. 

The workflow could have also changed and is automatically unassigning it from the developer as well. 

Like Dirk Ronsmans likes this

Hi @Dirk Ronsmans , when I move the task from Test to Ready to Release, this happens:

Ekran Resmi 2022-08-22 16.22.44.png

First, it looks like I assigned it to Merve (which was automatic actually, due to the rule). Then jira automatically removes the assignee.

Like Dirk Ronsmans likes this
Dirk Ronsmans Community Leader Aug 22, 2022

Allright so since the user is "Automation for Jira" we're 99% sure it's an Automation rule doing that :)

Can you go the Automation on that specific issue (should be on the right panel) and you can click thru to what rules have been running on that issue.

image.png

and when you click on the "Rule executions" you can see what rules were triggered.

 

image.png

First thing I would suggest to look there and see what rules are fire-ing. Then go thru those rules to see if any clear the assignee.

It's most likely an other rule than the one you created to set the assignee as the "rule actor" seems different (the automation user instead of you)

@Dirk Ronsmans I checked that screen, looks like my rule was executed:

Ekran Resmi 2022-08-22 17.38.04.png

There aren't any other rules which might have deleted the assignee.

 

Ekran Resmi 2022-08-22 15.55.57.png

But we have multiple developer fields for each task. Perhaps this is causing the malfunction. 

Ekran Resmi 2022-08-22 17.44.53.png

 

How can we create a proper transition rule for these?

Dirk Ronsmans Community Leader Aug 22, 2022

Could you also check the "Legacy Automation" on your project? You should find that in the Project Settings -> Automation -> Legacy Automation

I do wonder since you use {{issue.developer}} there should be field "developer" right? None of these 4 seem to correspond to that.

@Dirk Ronsmans I finally managed to fix it, thank you for your guidance :) 

Like Dirk Ronsmans likes this
Dirk Ronsmans Community Leader Aug 23, 2022

Feel like sharing what the issue was? Might help some other users and now I'm just curious ;-)

As you mentioned, there was a problem with the field names. We used to use the field "developer" on our previous board.

Now, we defined rules for these new field names separately and it started working again :) 

Our current rule looks like this:

Ekran Resmi 2022-08-23 16.55.09.png

Like Dirk Ronsmans likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS

Atlassian Community Events