How to make a carry over story only seen as done on most recent sprint

[Evan Hum]

When a sprint is completed, some stories may not be done and will get carried over to the next sprint. When those stories get finished in a new sprint, it will show as done in both sprints in both the Jira issue search and Jira custom dashboards. how can I only show the active sprint for those stories carried over?

[Hamza Chundrigar]

Hi @Evan Hum 

Welcome to the community.

It looks like the sprint field of those stories are carrying multiple values/sprint IDs. Is this something you can confirm?

As long as you remove all Stories that were not completed before closing the Sprint they will not keep the old values. The only time they will carry the value forward is if the Sprint is closed and they are moved (either to the backlog or the next Sprint).

Here’s another community post that might provide more insight into the nature and implications of your use-case.

Best,

Hamza 

[Bill Sheboy]

Hi @Evan Hum -- Welcome to the Atlassian Community!

I do not believe that is possible, due to the Sprint field's behavior of preserving the list of all sprints to which an issue was assigned.  Fortunately the built-in reports are accurate when showing when items finished.

A couple of possible work-arounds for what you are describing would be:

• Inside of Jira features: Use an automation rule and a custom field, which saves the "completed during" sprint using the Sprint Completed trigger.  You could then search and dashboard on that custom field.
• Outside of Jira features
  • Export the issues for reporting in another tool, such as a spreadsheet or report writer
  • Investigate marketplace addons with better reporting than Jira provides

Kind regards,
Bill

[Evan Hum]

Hi Bill,

Can you please elaborate on how to copy the field value

Regards, 

Evan Hum

[Bill Sheboy]

To do this with an automation rule, first you need to add a custom field to capture the "Sprint Completed".  If you have a team-managed project, the project admin can add the field.  If instead you have a company-managed project, discuss adding the field with your Jira site admin.

For the rule itself, this would do it:

• trigger: sprint completed
• branch: on issues in sprint
  • condition: check if the issue is "done"
  • action: edit the issue to set the custom field value to {{sprint.id}}

To get you started and learn more about automation rules, please look here:

https://www.atlassian.com/software/jira/guides/expand-jira/automation

[Evan Hum]

We have tried using the automation rule on Jira Dash Center, but the value isn't populating. Is this for Jira DC or Jira Cloud?

[Bill Sheboy]

That should work for Server/Data Center or Cloud.

In that rule you are showing, {{sprint.name}} will be the name of the sprint which completed and {{sprint.id}} will be the identifier.

What do you see in the audit log details when the rule runs?

[Walter Buggenhout]

Hi @Evan Hum and welcome to the Community!

Taking a pretty binary stand on this, an issue will not show as done in multiple sprints. It will just show as done. (period)

If you search in Jira and/or display search results on a dashboard, you are always looking at the current state of your issues, status being an important element of that state. So if your issue status is Done and you search for it now, that is the status you will see, even though the issue has been in multiple sprints. That is interesting and true information as well.

If you want to know exactly in what sprint the issue was closed or not, you can see that through the sprint report for the sprints you see listed on the issue.

Hope this helps!