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; } } }

need automation rule to notify when a field changes

Deb Keene

I want to analyze sprint field and be notified if:

a ticket is moved into a current sprint

a ticket is moved out of a current sprint

sprint value changes- a ticket was in sprint x and is now moved to sprint y

I am seeing rules for some pieces of this but cannot figure out how to handle all 3 scenarios. Would really appreciate some help

Accepted answers

Bill Sheboy

Hi @Deb Keene

What problem are you solving with notification of changes to the Sprint field? That is, "why" do this?

Until we know that...

The first two things on your list are already on the sprint report for company-managed projects as scope changes: issues added to or removed from an in-progress sprint: https://support.atlassian.com/jira-software-cloud/docs/view-and-understand-the-sprint-report/

For team-managed projects, those are shown on the burn chart reports: https://support.atlassian.com/jira-software-cloud/docs/view-and-understand-the-team-managed-sprint-burndown-chart/

The third thing (changing sprints) can overlap the first two categories; for other cases (such as a REST API change which both removes and adds a sprint), there is no such reporting...and it may have less meaning if none of the sprint value changed were the in-progress sprint.

If you still want notification as soon as the field changes, there is a challenge doing that: there are known defects with automation rule usage of the changelog for list fields like Sprint. And so workarounds are required, such as using another field to track sprint scope. For example:

create one rule, triggered on sprint started, which adds an indicator label for "in_current_sprint" to the issues in the sprint
create another rule, triggered on sprint completed, which removes the label
create a third rule, triggered on changes to the sprint field, which uses the label field and JQL to detect additions / removals from sprint scope

These would handle your first two cases. There may not be a way with built-in features to see the third case unless it overlaps the first two.

Kind regards,
Bill

All comments

Bill Sheboy

Hi @Deb Keene

What problem are you solving with notification of changes to the Sprint field? That is, "why" do this?

Until we know that...

For team-managed projects, those are shown on the burn chart reports: https://support.atlassian.com/jira-software-cloud/docs/view-and-understand-the-team-managed-sprint-burndown-chart/

create one rule, triggered on sprint started, which adds an indicator label for "in_current_sprint" to the issues in the sprint
create another rule, triggered on sprint completed, which removes the label
create a third rule, triggered on changes to the sprint field, which uses the label field and JQL to detect additions / removals from sprint scope

These would handle your first two cases. There may not be a way with built-in features to see the third case unless it overlaps the first two.

Kind regards,
Bill

Deb Keene

The person who manages our sprint tracks number of items we have in beginning of sprint- how many tickets are added during the sprint, taken out during the sprint, etc and wants to be notified if anything is updated during sprint. I know we could take away every ones permissions to update sprint but that was not what people wanted so we are trying to monitor instead.

Ideally we would have an automation rule that would notify this person when anyone changes the sprint field so would not want to use the standard reports offered in the tool- burndown.

https://support.atlassian.com/jira-software-cloud/docs/view-and-understand-the-sprint-report/

the report shown at bottom of this page- showing number of completed items, etc is not easily exported for further analysis

Bill Sheboy

Thanks for that information, Deb. Perhaps try the three automation rules I described, where the third one can send the notifications of add / remove scope.

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-service-management-cloud

jira-service-management