How to find and define the correct Smart Value

Question

Hi!

I am trying to create a rule where for every ticket that is created, the automation should look at the date in which the issue was created as well as the start date of the sprint and make a decision. For example, if a ticket is created and put into the sprint on the first day, this rule should be bypassed, but if a ticket is created and put into an active sprint on any day AFTER the first, it should trigger the rule and make a decision (alert the reporter).

We are looking at a specific custom field, "Type of Request". Tickets created after the first day of the sprint should have a specific type of request selection. But I cannot help but trigger the action regardless of the smart value, so I am not sure what is the issue.

Bill Sheboy · Answer

Just to clarify on the multiple sprints / carry-over issue: if your team clones issues and selects the checkbox to clone the sprint, the sprint value(s) will be propagated.

Using the JQL condition approach, I provided the JQL in my first response and the condition type to use is this one:

https://support.atlassian.com/cloud-automation/docs/jira-automation-conditions/#JQL

Hector Sibisi · Answer

@Bill Sheboy Thank you so much.

For this scenario, we are only considering newly created/updated issues, so the rollovers would stay as they are. But you've made me think of things I hadn't considered.

Also, I wonder if there is a scenario where we only look at the {{sprint.startDate}} regardless of whether the sprint is active. Sometimes, my team creates issues before the sprint starts and then updates the required fields, so it's possible that a ticket created will not be placed into an active sprint, but we still have to comment on the issue. Is JQL still the best way? Can you show me an example, maybe?

Here are checks:

- For Planned tickets, to check if the issue is created or put into the sprint on the first day of the sprint.

I also looked at the abovementioned links and this is how I decided on the smart values for this, so please look at the attached image and let me know if I've missed something.

-

Bill Sheboy · Answer

Yes: you could use the date / time difference function for that: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-date-and-time/#Date-difference---

Or, convert the values to text and then perform the comparison: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-date-and-time/#Date-format---

I still recommend the JQL approach for your scenario.  The reason is when an issue is carried over from one sprint to another (if it was not completed), the sprint field will then contain multiple sprint values.  It is not simple to identify the correct sprint in the field for the date comparison.