Change the status from the backlog to To Do when assigned to a user

[Lena Sargsyan]

Hi,

This time my question is about automation.

Say, I have unassigned issues in the backlog - I want the automation to transition them to To Do status when I assign them to a user. How can this be done please advise?

Thank you

[Tobias H]

Hi Lena!

You should be able to do this easily by the following three steps

1. When: Issue Assigned
2. IF Status equals Backlog
3. Then Transition issue to To Do

[Tobias H]

Sorry, I missed the part that assignee is empty.

Use the If/Else block instead like this:

[Sam Nadarajan]

Hmm I'm not seeing the part where the ask was the assignee was empty, I think your first screenshot was correct?

[Mark Segall]

Just a quick note on this... The condition assignee is empty will not apply to the Issue Assigned trigger.  The rule will only fire when the issue is first assigned so there would be no possibility that the assignee is empty.

[Tobias H]

Thanks @Sam Nadarajan and @Mark Segall 

I think I read into it too much when I came back and posted my first reply :)
(This part: "Say, I have unassigned issues in the backlog")

Also, @Mark: Was not aware that the "Issue Assigned" could only be triggered when an issue is unassigned, thought it might potentially go of when it was switched between people as well.

Either way, there is very few possibilities where the issue would be in the Backlog and need to be assigned, after initial assignment, so the first automation should work fine :D

[Mark Segall]

Hi @Lena Sargsyan - You'll want something like this:

• TRIGGER: Issue Assigned
• CONDITION: Status = Backlog
• ACTION: Transition issue (to To Do)

[Lena Sargsyan]

Thanks to all! Before You answered I had tried this way, and now it works. But since your answers are different from mine I started to doubt: what if it is conflicting with other cases?

[Tobias H]

That works as well, it's just that there exists a "Issue assigned" trigger by default, so there isn't a need to create it manually through the Value change :)

[Mark Segall]

Yes the field value changed trigger approach will work as well.  However, in this instance, you may want to include the condition that the assignee is not empty that @Tobias H had. 

The difference between these two triggers is that issue assigned is when the issue is assigned to a user vs field value changed where it'll fire every time the assignee field is changed, including when the assignee is removed.