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)
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.
I found that a suggestion has been opened for Release Burndown for Kanban, but only for JIRA server, not for JIRA Cloud.
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.
Catch up with Atlassian Product Managers in our 2020 Demo Den round-up! From Advanced Roadmaps to Code in Jira to Next-Gen Workflows, check out the videos below to help up-level your work in the new ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events