Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Automation: targeting by JQL the same user as in a triggered rule Edited

Greetings, I'm trying to create simple automation to pull out all tasks of a person from one status to another when someone moving in a new task to that status.

Goal to ensure that each person couldn't have more than 1 task at the same time in that particular status.

Currently, I've managed to create a rule which pushes away all tasks in that status, now I need somehow to capture the 'assignee' field from the trigger issue and via JQL search for his/her tasks and move them (or any other way, which helps me reach the goal).

Project automation - Jira - Mozilla Firefox 2021-0 (5).png

1 answer

1 accepted

1 vote
Answer accepted

Hi @Alexey 

First thing: I wonder if you are solving a symptom or a root cause of the problem, which appears to be people are not finishing work before starting more work, leading to higher work in progress (WIP).  Solving the symptom using Jira automation may lead to unintended consequences: such as people not assigning work or moving it when active.

For your question, have you looked at {{triggerIssue.assignee}} as a field to use for queries?

Best regards,
Bill

Thanks, @Bill Sheboy there are a couple of scenarios of why this happens but at the end of the day, it's all about transparency. We need to see what people are doing, to make decisions. As a team, we decided to test such automatic assistance and see how it goes.

Back to the topic, as I know JQL does not accept smart values, hence I don't know a way to add {{triggerIssue.assignee}} to the query.

In my understanding, I need to compare {{triggerIssue.assignee}} with JQL results and at this moment, I do not know how to do that!

Inside of an automation rule, you can use smart values in JQL.  For example, you can branch or do a Lookup Issues on:

assignee = {{triggerIssue.assignee}}

You cannot test it with "verify" when writing the rule, as the smart value isn't populated yet.  Instead you would need to run the rule to confirm your results.

Like Alexey likes this

@Bill SheboyThanks a lot, i wasn't aware of the ability to use smart values in JQL within automation rules! Learning new every day hehe, it works, perfectly.

Maybe it's not the most elegant way to handle WIP, but we need time to adjust our processes and this is what everyone has been asking.
I added an exception for unassigned tasks, but we cant have such issues at that stage.

Like Bill Sheboy likes this

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Trello

🏊‍♀️ Atlympic Event: Trello

Hello Community!  Quick disclaimer: We are running a contest on Community (The Atlympics!) from July 23rd - August 8th of 2021. If you are interested in participating in this contest (prizes! ...

112 views 1 12
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you