Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Is there a way to autoassign a subtask via automation based on a multi text field?

Has M. February 28, 2023

I have an automation that I created where it creates several subtasks based on a value on the custom fields. It is working pretty well, but I added a condition to create a subtask and auto-assign to a user for a text field and it's not working. I tried the values to set to "is not equal to" and "is not empty but neither is working. 

Is there a way to create a subtask and auto-assign it to a user when the field value is not empty?

 

1 answer

0 votes
Mikael Sandberg
Community Champion
February 28, 2023

You should be able to do it by using the JQL condition, something like this:

description is not EMPTY

Has M. March 1, 2023

Thank you. I will try that.

Like Mikael Sandberg likes this
Has M. March 1, 2023

Unfortunately, that didn't work.

Mikael Sandberg
Community Champion
March 1, 2023

What is not working, the JQL or your automation? I just tested this automation in my sandbox and it works as expected:

Screenshot 2023-03-01 at 12.37.10 PM.png

Some of the components do not support searching on empty values, like the issue lookup one, but the JQL condition in the if/else one does support it.

Has M. March 2, 2023

@Mikael Sandberg Thanks for looking into this and your input.

This is how I have it set up: I have a bunch of subtasks that are suppose to be created based on the values on the custom fields and then auto-assign to specific users. I have tested this against fields which are select list/multi-select list/text field. The Subtasks are getting created based on the value of the custom field but this particular field is a text field and the automation didn't create the subtask. Below are a few screenshots of some of the parts of the automation...

 

NHOF-atuoamtion1.png

.

.

NHOF-atuoamtion2.png

 

 

The top two fields are select lists whereas the Accountabilities field is a text field.

 

I am also having another issue where whenever the ticket is updated, this created duplicate subtasks. I know why it's happening but I haven't figured out a solution for it yet.

Mikael Sandberg
Community Champion
March 2, 2023

Okay, instead of the issue field condition, use the JQL one see if that helps, similar to what I did in my test automation above.

Has M. March 2, 2023

Thanks @Mikael Sandberg

This is what I tried and it didn't work either.

 

NHOF-atuoamtion3.png

Mikael Sandberg
Community Champion
March 2, 2023

If you check the audit log, what does it say when you get to checking if Accountabilities is not empty?

Has M. March 2, 2023

It says that the issue didn't match the condition even though I updated the field.

NHOF-atuoamtion4.png

 

NHOF-atuoamtion5.png

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events