nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Automation rule if Status is not used

mborinstein

I have created a custom field called "In Progress Start Date" and set up Automation so that when a ticket moves to the "In Progress" status the field populates with the date it moved to that status.

Every now and then, an engineer may forget to move a ticket into "In Progress" and instead move it directly to "In Review" or another later status on the board. How could I use Automation rules so that if the ticket never goes into "In Progress" it will fill the date of when it enters "In Review" instead?

Accepted answers

Bill Sheboy

Hi @mborinstein

There are at least two ways to help with this scenario:

1) Update the workflow so items must go through the "In Progress" status first. This would act as a reminder when someone tries to move straight to "In Review".

2) However...if they forgot, as you describe, #1 will not help. Assuming both the "In Progress" and "In Review" statuses both have an "In Progress" status category, you could do use the statuscategorychangeddate smart value to help:

trigger: work item transitioned
condition: check if your "In Progress Start Date" field is empty
smart values condition: check when in an in progress status
- first value: {{issue.statusCategory.name}}
- condition: equals
- second value: In Progress
action: edit work item, setting your field with...
- {{issue.statuscategorychangedate.toDate}}

Kind regards,
Bill

All comments

Bill Sheboy

Hi @mborinstein

There are at least two ways to help with this scenario:

1) Update the workflow so items must go through the "In Progress" status first. This would act as a reminder when someone tries to move straight to "In Review".

trigger: work item transitioned
condition: check if your "In Progress Start Date" field is empty
smart values condition: check when in an in progress status
- first value: {{issue.statusCategory.name}}
- condition: equals
- second value: In Progress
action: edit work item, setting your field with...
- {{issue.statuscategorychangedate.toDate}}

Kind regards,
Bill

mborinstein

Thanks Bill! Would you create this as an additional, separate rule or would you add it on to the existing rule I have in place?

mborinstein

I also have a very similar situation where I currently have a custom field get filled when a ticket moves to "Ready for Release". It's possible that an engineer skips that column and moves the ticket straight to "Done". In that case the "Ready for Release" field is an "In Progress" status category but "Done" I assume is another status category. How would you recommend adjusting your rule for that scenario?

Bill Sheboy

Hi @mborinstein

For your first question, the rule I suggested could be used to replace your existing one to set the field.

For your second question about the "Ready for Release" and "Done" statuses, I expect those are different categories. You could use a different rule for that which just checks the destination status to set the field, such as with:

trigger: work item transitioned
- where the "to status" is either "Ready for Release" or "Done"
condition: check if your custom field is empty
action: edit work item, setting the custom field to {{now}}

Please note well: These rules you are creating seem to be in support of reporting different events in the life of the work item. Everything is okay when rules are running as expected, however when Atlassian has an incident / outage impacting rules, the values of the dates captured may not be accurate. Worst case, the rules may not run at all to "catch up" after the outage. In that case, you may need to do some manual clean-up by reviewing the work item histories.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

automation

jira-automation