Automation not working

[ozgeseckin]

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?

[Dirk Ronsmans · Accepted solution]

Hey @ozgeseckin ,

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

[Heather Ronnebeck]

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. 

[ozgeseckin]

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

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

[Dirk Ronsmans]

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.

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

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)

[ozgeseckin]

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

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

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

How can we create a proper transition rule for these?

[Dirk Ronsmans]

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.

[ozgeseckin]

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

[Dirk Ronsmans]

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

[ozgeseckin]

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: