Just a heads up: On March 24, 2025, starting at 4:30pm CDT / 19:30 UTC, the site will be undergoing scheduled maintenance for a few hours. During this time, the site might be unavailable for a short while. Thanks for your patience.

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

Jira field value change to trigger only when the field was updated when it was non-empty

Jignesh Jaiswal
Contributor
October 11, 2023

Hi Team, 

 

I am trying to add a Label value when the "Due" field was updated from one to another date, however the "Field value change" rule runs for the first time update from empty to any value. How to run this rule only when there is value in "Due" and is changed?

1 answer

1 accepted

1 vote
Answer accepted
Jack Brickey
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
October 11, 2023

Hi @Jignesh Jaiswal , Indeed, this is the behavior of this trigger. Unfortunately, that cannot be changed. However, there are ways to accomplish your goal I think. One option would be to create a custom date field that captures the original due date. This could be populated using the same rule. Basically, when the rule was triggered, it could check to see if the original due date field was empty or not. If it is copy the due date over, if not leave it alone but perform whatever other actions you intended if someone is changing the due date.

note, if you don't want to create a custom field, you could consider using a label in a similar fashion.

Jignesh Jaiswal
Contributor
October 12, 2023 edited

hi @Jack Brickey Thank you for the workaround. However, I could update the secondary date field, but cannot still update the Label on 2nd change of Due Date change. PPDEmpty.png

Jack Brickey
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
October 12, 2023

Hi @Jignesh Jaiswal , i'm not sure I understand the issue. Are you saying that the last component where you attempt to add a label is unsuccessful? Please be sure that the label exists before using in your automation rule. Can you share the audit log?

Jignesh Jaiswal
Contributor
October 12, 2023

hi @Jack Brickey Please ignore it, I could fix it. I had to use ifelse and split the condition when the Due was empty and non-empty. It works now as expected. Thanks for your timely inputs as this solved this open item for me.

Like Jack Brickey likes this
Vicky S April 1, 2024

Hi @Jignesh Jaiswal , i m looking for the exact use case as you have , can you share the detailed rule flow which was successful for you ? 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
atlassian, atlassian community, journeys for jira service management, journeys for jsm, eap jsm atlassian, early access program atlassian, early access program journeys atlassian, early access program journeys jira service management, join atlassian eap

Join the Early Access Program (EAP) - Journeys for Jira Service Management 🚪

Journeys is a brand new feature in Jira Service Management that helps you streamline various processes in your organization that may cross multiple departments, such as employee onboarding or off-boarding that require action from different teams. ✨

Join the EAP →
AUG Leaders

Upcoming Jira Service Management Events