#3591 RFE - roadmap page - add option to ignore milestones that do not have any open issues in them
Closed: Fixed 2 years ago Opened 2 years ago by mreynolds.

For projects like 389-ds-base where we have a hundred milestones the road map page is really busy with milestones that we don't care about (that have no open issues). The old UI had ways to filter these out, and do other things like sorting my tag, etc. It would be nice if some of these features were also in the new UI.


There kinda is filtering already for this, with the active / inactive milestones thing. The idea here being that when something is complete, it is marked as inactive, and doesnt show in the main view.

With the tags, what would be your use-case for searching by tags here? the new issues search has the ability to filter by milestone and / or tag too.

since we have the view now being listing the milestones, and drilling down into the milestone detail, not sure if filtering by tag on the milestones list would be helpful. In the drilled down, we could def add some additionally filtering there for sure.

https://stg.pagure.io/389-ds-base/roadmap?status=active

What defines a milestone as active?

Almost all the milestones do not have active/open tickets, but they are still listed. This makes the roadmap unusable in my opinion when 95% of 150+ milestones do not have open tickets under them. How do I know which milestones are truly active and have open issues that need to be addressed? In the old/current UI we heavily rely on this when triaging tickets to engineers.

I'm not worried about the tag sorting, but it was nice to have. But the issue with listing milestones that do not have open issues in them is way more important to us.

What defines a milestone as active?

Admins do, in the settings page of the project :)
We added a patch fixing toggling showing/hiding the inactive milestones (hidden by default) on that page

Metadata Update from @pingou:
- Issue set to the milestone: 5.0
- Issue tagged with: RFE

2 years ago

What defines a milestone as active?

Admins do, in the settings page of the project :)
We added a patch fixing toggling showing/hiding the inactive milestones (hidden by default) on that page

I guess my point was that it used to be automatic. The roadmap previously showed only the milestones with open tickets. Your suggestion still requires me to look through ALL the milestones everyday and set which ones are what I would call "active" (milestones with open tickets), and which ares aren't. That is not a good workaround when you have 150+ milestones. :-)

Anyway, I hope this change makes it into the new UI, thanks!

i think the idea of the active thing was to provide a point that a project manager could manually define the milestones being worked on, i.e. everything that is not released, and being worked on currently is active, while ones already released are inactive.

Since, a milestone that is currently in development, i.e. active, may be marked as 100% complete, but more issues may be assigned to it sometime in the future.

Just out of interest, how many milestones in your 150+ are actually being developed on at this time?

That said, it should be pretty easy to add a filter to the list on https://stg.pagure.io/389-ds-base/roadmap to show milestones with a completion of less than 100%.

That is the datapoint you are most interested in here, right? milestones that have open issues on them?

okies, have a proof of concept PR #3598 that adds some filters to the roadmap milestone list page:

Peek_2018-08-30_21-29.gif

This allows you to show only incomplete (i.e. not 100% -- milestones with open bugs in them). It also allows you to filter the list of milestones by the query of the milestone name.

Just out of interest, how many milestones in your 150+ are actually being developed on at this time?

It varies, but it's usually around 5 milestones. But when issues pop up on older versions the list gets larger, and we don't want to miss those tickets.

Looking at your gif, that should work! But why is a milestone with 0 issues being shown? :-) Either way that would not cause a problem, just an observation.

Thanks!

yeah, that was deliberate, not sure how to handle that to be honest, its not technically 100% complete if there are no issues (depending how you look at it) :)

would it make more sense to you to hide the 0 issue milestones with this toggle?

also, considering adding the completion percentage next to the issues count before the bar too, so you can see the percentage without hovering.

Metadata Update from @ryanlerch:
- Issue assigned to ryanlerch

2 years ago

Metadata Update from @ryanlerch:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

2 years ago

Login to comment on this ticket.

Metadata
Attachments 1