nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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?

Ekran Resmi 2022-08-22 15.55.57.png

Accepted answers

Dirk Ronsmans

Hey @ozgeseckin ,

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

All comments

Dirk Ronsmans

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:

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.

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)

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud