Heads up! On March 5, starting at 4:30 PM Central Time, our community will be undergoing scheduled maintenance for a few hours. During this time, you will find the site temporarily inaccessible. Thanks for your patience. Read more.

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

Set-up Automation Rule when changing specific issue types to check certain fields are not empty

Melissa.Breen
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
June 5, 2023

Hello- having trouble trying to navigate my automation rule set up.  Not sure I can accomplish all or any of what I'm looking to do.  I've noted and option 1 or 2 on the output of the rule below- open to either.  Here is what I'm looking to do.

When: user changes the issue type from Feature to Story 

Check that fields Epic, Story Points, Workstream and T-Shirt Size are not empty

If all are populated, then no action

Option 1) If 1 or more of noted fields are not populated, then provide this error message:

"please check that the following fields are populated..."

or

Option 2) no error warning, just do not allow the issue type change to proceed

1 answer

1 accepted

0 votes
Answer accepted
Mark Segall
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
June 5, 2023

Hi @Melissa.Breen - Automation is intended for actions.  The best you'd get from it would be maybe creating a communication (comment, slack/teams message, email) when those items aren't populated.

I'd recommend instead having validators in your story workflow to ensure that the user cannot transition the issue until those fields are populated.

Melissa.Breen
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
June 5, 2023

Thx @Mark_Segall- I was afraid of that- I am also placing validators in the second workflow but we were trying to catch this up stream as the switch in types is to be ready for the second flow which all these items are mandatory to have in place.  Appreciate the input- at least I can stopped digging and wasting time trying to figure out if I'm missing something ;)

Suggest an answer

Log in or Sign up to answer