search

codetree / feedback

A central hub for user feedback for Codetree
https://codetree.com
20 stars 15 forks source link

Showing closed Milestones while in List view #218

Open leonardfactory opened 8 years ago

leonardfactory commented 8 years ago

Actually I'd like to have a top level view of past and future tasks in the List View, having all issues ordered and grouped by milestones. However whenever I filter by closed & open issues or just closed issues, the ones in a closed milestones do not show up.

I'd like to see even closed Milestones, maybe as a new filter, in order to have a past view on activities.

Furthermore, closed Milestones seems to be hidden generally in the List View, even when applying the milestone filter.

Surely I understand that closed milestones may be just garbage in the day by day work, so maybe an optional show open & closed milestones filter would be very appreciated.

kareem commented 8 years ago

Great suggestion. Can you help me understand the use case for going back to look at issues in closed milestones? I have some ideas but want to know what's important to you about it.

Thanks!

On Fri, Oct 7, 2016 at 11:30 AM, Leonardo Ascione notifications@github.com wrote:

Actually I'd like to have a top level view of past and future tasks in the List View, having all issues ordered and grouped by milestones. However whenever I filter by closed & open issues or just closed issues, the ones in a closed milestones do not show up.

I'd like to see even closed Milestones, maybe as a new filter, in order to have a past view on activities.

Furthermore, closed Milestones seems to be hidden generally in the List View, even when applying the milestone filter.

Surely I understand that closed milestones may be just garbage in the day by day work, so maybe an optional show open & closed milestones filter would be very appreciated.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/codetree/feedback/issues/218, or mute the thread https://github.com/notifications/unsubscribe-auth/AABmC7Vq8SiiV1wbZd7KHkxprLunaaxjks5qxo_RgaJpZM4KRU2S .

leonardfactory commented 8 years ago

I use this in order to check team productivity, so I'm comparing:

Especially the last one needs a way to check closed milestones performance, in order to re-arrange points estimation ahead of time if we see something isn't going as planned (more effort needed, due date anticipation, etc.)

An example:

We've done 100points in the first sprint. The second sprint requires 120 points, but we hired a new dev, allocated only on this project. We strike to achieve a 150points productivity with him, so at the end of the third month we'd like to see if it's true. After this check, we can re-arrange tasks on the third sprint in order to:

  • Have more effort available on other projects from the new dev
  • Accelerate project development and anticipate iterations

Feel free to ask for more details if this could be helpful for CT. This is a methodology, but I think it's pretty common, with some variations, between teams.

kareem commented 8 years ago

This seems like it's probably two issues. One issue is that you are trying to understand capacity planning (Planned activities roadmap), changes in velocity (Task completion evolution), sprint velocity (Total task points done in a sprint) and estimate quality (Points estimation vs real allocation). Each of those could be a feature on their own.

As a workaround you could do it manually except Codetree filters all issues from Closed Milestones. We're investigating this issue for now.

kareem commented 7 years ago

Related to https://github.com/codetree/feedback/issues/230#issuecomment-274048022