How to track scope change in a release

[Rahul]

How to track scope change in a release?

Number of issues added or number of issues removed aftr release start?

[Mary from Planyway]

Hi @Rahul 

It's Mary from Planyway team

Tracking scope change in a Jira release involves monitoring the number of issues added or removed after the release start. This is critical for project management, as it helps in understanding how changes affect the release timeline and workload. Here's how you can track scope changes in a Jira release:

1. Using Jira's Built-in Features

• Versions: Jira allows you to assign issues to a specific "Version," which is often used to represent releases. If you're using versions, you can easily see how many issues are added or removed by looking at the version report.

• Dashboards and Gadgets: You can create a dashboard and use various gadgets to track scope changes.

  • Filter Results Gadget: Use this to display issues added to the release. You can create a filter for issues with the version set to your release and use the "Created date" to track when new issues are added.
  • Two-Dimensional Filter Statistics Gadget: This gadget can help visualize the number of issues added or removed based on status, priority, or other fields by setting one axis to the "Fix Version" and the other to the criteria you're interested in.

2. Custom JQL Queries

• Issues Added After Release Start: Use Jira Query Language (JQL) to find issues added to a version after the release start. For example:
  
• Issues Removed From Release: Tracking removed issues can be tricky, as Jira does not directly track when an issue is removed from a version. However, you can use workarounds, such as creating a custom field to log when an issue is removed from a release or tracking history via issue audit logs if available.

3. Automation

• Automation for Jira: If you have Automation for Jira (available in Jira Cloud and some Server/Data Center versions), you can set up rules to log or track when issues are added or removed from a version. For example, you can create an automation rule that adds a comment or updates a custom field whenever the fixVersion field is changed.

4. Reports and Gadgets

• Version Report: This report shows progress on a version, including issues completed, issues remaining, and any scope change. It's a built-in report in Jira Software projects.
• Release Burndown Chart: The release burndown chart helps you track the progress towards completing a version, showing added and completed work over time. It's particularly useful for Agile projects to visualize scope changes.

[Bill Sheboy]

Hi @Rahul 

Are you using a Scrum board?  If so, you may try these built-in reports to see the changes for a release:

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

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

Kind regards,
Bill