Creation of a trigger in JIRA Automation, using LABELS

[Amitava Mallick]

I am wondering if a trigger can be added in JIRA Automation using a specific LABEL

1. There is a ticket AB-1, already taken in the sprint

2. in the LABEL field, a certain label called as WISHLIST is put and ENTER pressed

3. The automation automatically send that ticket out of the sprint directly to the BACKLOG

4. Till the time, the LABEL "WISHLIST" is on the ticket AB-1, it can never be taken into a sprint. Even if someone mistakenly pulls it into a sprint, the automation sends it back to BACKLOG

Please help suggest a way

[Dawid Joshua _TechTime_]

This automation rule should do what you want: 
 

1. The trigger when a value is added either to Label or Sprint field. 
2. Condition checks if label "wishlist" is present on the ticket.
3. And if yes, it clears the Sprint field, effectively moving it to Backlog. 

[Amitava Mallick]

We have Kanban Board, and there is NO SPRINT for one of the project. What to do in that case?

[Bill Sheboy]

Hi @Amitava Mallick 

What problem are you trying to solve by doing this?

I am asking as you note using sprints, which may indicate your team is using Scrum and sprint planning to decide what to work on each sprint.  If adding a label to an issue can alter that plan, that may be a symptom there is a problem with backlog refinement and/or planning: why pull in something for delivery which could be removed?

Thanks and kind regards,
Bill

[Amitava Mallick]

Hello Bill,

Apologies for the delay. You are absolutely right , however all our Customer Success team works on Kanban principle, and they work on multiple projects with tickets at the same time. Now though it is not possible to work on them simultaneously, there might be some tickets which need to be sent to backlog even after being taken for work, due to research/ pending clarification from clients and son on.

Therefore I was asking if this automation can be done

[Bill Sheboy]

Thanks for explaining the situation.  You may want to consider either:

• using Kanban methods (including the Jira board) and/or
• making specific items to research/clarify a request.  Those could be moved to "done" after the research, with a linked, new backlog item to implement the item added to the backlog for later consideration.  This would eliminate the need to change the sprint scope.