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

How to report on resolved tickets based on filter results?

Lisa Hagemann

Scenario: I have a custom filter which identifies tickets assigned for the next release ("fixVersion changed TO earliestUnreleasedVersion() AFTER -90d"). I want to track the progress on resolving these tickets.

I want something similar to the Created vs. Resolved display, but for my case created is not really meaningful (ticket could be a year old, and only just pulled into the next release)

I'd want to see that -90d there were 0 tickets with `earliestUnreleasedVersion` and over time tickets were added into the release, and we started closing them. And showing the delta of work still to complete.

I'm also particularly interested in showing if tickets get added into a release.

I am using the Classic Software project, and Kanban. (no Sprints)

Accepted answers

Trudy P Claspill

Hello @Lisa Hagemann

Are you using a Classic project or Next-Gen project?

If Classic, are you using a Scrum or Kanban agile board?

If you are using a Classic project and Scrum agile board, you should have access to the Release Burndown report. I don't think it is quite what you're looking for, but maybe it will be useful.

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

All comments

Trudy P Claspill

Hello @Lisa Hagemann

Are you using a Classic project or Next-Gen project?

If Classic, are you using a Scrum or Kanban agile board?

If you are using a Classic project and Scrum agile board, you should have access to the Release Burndown report. I don't think it is quite what you're looking for, but maybe it will be useful.

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

Lisa Hagemann

Hi Trudy,
Thank your for your reply. I edited my question to include answers to your questions. I am using Classic project and Kanban.

I thought about the Sprint burndown, I'll read the doc you linked. But since we are not using sprints I'm not hopeful.

Trudy P Claspill

I found that a suggestion has been opened for Release Burndown for Kanban, but only for JIRA server, not for JIRA Cloud.

https://jira.atlassian.com/browse/JSWSERVER-15617

You could also actually set up a sprint agile board against your project/filter just to get the Release Burndown report. You don't have to use the Scrum methodology for your project, and you could continue to manage the workload through your Kanban board.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud