project = [project.name] AND Sprint != [sprint.code] and status = Closed and issue not in closedSprints () If the sprint referenced by [sprint.code] is closed and this query produces a result, inspect the history of the issues. They were likely closed outside of the sprint time box. For non-story issues, using a Resolution of Won't Do or Cancelled will not affect the velocity in any way. For story point estimated issues in the current sprint, I prefer teams remove the item from the current sprint, returning it back to the backlog, first. This will de-scope the item from the current sprint, prior to marking it Won't Do or Created Vs. Resolved Issues Report: Shows the number of issues created as opposed to the number of issues resolved over a period of time. Pie Chart Report: Shows the search results from a specified issue filter (or project) in a pie-chart, based on a statistic of your choice. Resolution Time Report: Shows the average time taken to resolve issues.
It is not a compulsory field in JIRA, yet it is very helpful in reflecting the health of the project via the Created Vs Resolved Report which was discussed in a previous article on JIRA Reporting Options. It is set at the time of changing the status to Resolved and it explains why an issue may be resolved.
In order to change a resolution from fixed to unresolved in Jira, you first need to navigate to the issue in question. Once you are viewing the issue, you will need to click on the “Actions” drop-down menu, located towards the top right-hand side of the screen. From the “Actions” drop-down menu, select the option “Resolve issue” and
