We're using components to track subprojects. All is fine with that approach, until we try to use the Reports option. For instance, I'd like to see the velocity of one particular subproject.
Every report is only showing the results of the board under review, and that board is displaying based on the configured filter. So, we *are* able to show a burndown or velocity for example, for a single subproject.
That said, why the cumulative flow diagram allows for OTHER filters to be used, I don't know. I like that feature and would like to see it on other reports but it is not a show-stopper for us.
I'm having a similar challenge which adding filters to all the reports would fix. Specifically, we use the Version Report to project completion of a release, but I'd like to exclude issues resolved as Won't Fix or Duplicate because they artificially inflate our velocity and thus provide an overly optimistic release date estimate.
It is interesting that filters are available in the Cumulative Flow Diagram but not for the rest of the reports.
UPDATE: Per your comment that there is a level of filtering going on already based on the board filter, I created a separate board that excludes all Won't Fix and Duplicate issues. This works and gives me the estimate I'm looking for, but it feels like a very cumbersome solution.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs