[Projects Beta] [Insights] Option to include/exclude archived issues for charts #13356
Replies: 4 comments
|
Regarding removal from all charts I have no opinion. Regarding retroactive removal from Time series charts e.g. Burn Up / CFD |
|
Despite having now access to more items on the board (50k), the issue remains. We still have to remove old items from our views (aka archive) because it clogs up the views and makes the boards very slow. With archived items though, these dashboards are essentially useless (we'd love to see some stats but the stats shown are wrong because the majority is filtered out). |
|
Still an issue! |
|
If a paid add-on is an option, I suggest taking a look at the Analytics & Reports by Screenful. It will keep the archived items in the stats so you can track your metrics over longer periods of time. Here's a list of metrics you can track with Screenful. Available in the GitHub Marketplace. |
Uh oh!
There was an error while loading. Please reload this page.
The way charts handle archived issues limits the effectiveness and flexibility of charts/insights. I think there are two main improvements that would be helpful:
Handle archived issues consistently
The behaviour for including archived issues seems to be inconsistent right now.
When I look at the Burn up / CFD default chart, all archived issues appear to be included in the visualization. In my case, that meant the chart wasn't useful to me (since it isn't configurable), as the data is completely dominated by completed archived issues. I had to create a duplicate chart with a filter to get useful data.
Seeing that archived issues are included, I tried to use that behaviour to make a chart that shows velocity over time (i.e. Sum of
Points(number),status:Done, plotted perSprint(iteration)). But as soon as I archived items from the previous sprint, they were excluded from the chart.Now I don't know what behaviour to expect, or if I'm doing something wrong. I think the behaviour should be consistent: probably including archived issues by default. But I think it's even more important to be able to control this behaviour.
Give the user control over archived issue inclusion
As described above, there's a need to include or exclude archived issues on a per visualization basis.
I think there are a couple ways this could be made available:
is:archivedproperty we can use for filters (e.g. include by default, add-to hide)Note on workarounds
I'm guessing this issue can be mostly worked around by creating some sort of "Archived" status and then filtering on it to include in select visualizations and hide from basically all other Projects Beta views. But that essentially re-implements and replaces the true archival feature, which signals to me that this a feature worth adding.
All reactions