onespot/enhancedgi

A project forecasting tool that integrates with Github Issues

enhancedgi's Issues

Make milestone planning respect weekends

Extend planner to work with other repositories and educate team about labeling

Click on milestone in Gantt chart to edit

Clicking on a milestone should bring you to the edit milestone page because it's rather hard to find it otherwise:

https://github.com/onespot/amplify-back-end/issues/milestones/6/edit

priority syntax is fragile

If I type:

priority: 5

Instead of:

priority:5

It doesn't work.

Create simple reports based on the github issues api

cc: @sanity
see here https://github.com/onespot/enhancedgi/wiki/User-Stories for user stories

Email developers about improperly labelled issues every day

If a developer has issues without milestones or time estimates, they should be emailed every day to pester them to sort this out (probably at midnight Central time so it's there for them when they wake up).

Allow assigning of milestones and people to tickets on right click

Treat milestones in seperate repos with the same name as the same

Update milestone dates dynamically based on estimates

The completion dates of milestones should be updated automatically based on the total estimates of the issues assigned to those milestones.

I think we have to be smart about how milestones are prioritized though. This could be done through dependencies, or alternatively just through some text like:

priority:5

In the description of the milestone. To determine milestone completion dates I think an algorithm like this might work:

Firstly assign the priority of the milestone to each issue that is part of that milestone (if we have dependencies then we'll need a first-pass to assign priorities based on these)

Secondly, for each developer sort all of the issues assigned to them according to priority (so highest priority gets done first). For issues with the same priority, those for the same milestone should be grouped together.

Lay these out on a timeline considering 5-day work-week etc. so we know start and end dates for each priority.

Then for each milestone, find the earliest date when all of the issues for that milestone are (estimated to) be completed (remembering that multiple developers may be working on the issues for any given milestone), this will be the milestone completion date.

Use a different color for task bars depending on milestone

Eg. milestones ending with "1.0" should be a different color to "2.0" etc.

Store config preferences in a cookie

Might be more intuitive to store configuration preferences in cookies (ie. what repos to include) - although I see that you can just bookmark the entire GET request, this is less intuitive.

Need a way to prioritize milestones/features

Support dependencies between milestones and issues

We should support dependencies between issues and issues, milestones and issues, and milestones and milestones, including dependencies across repositories. This may be done with a syntax like this in the descriptions:

depends: i2 - Depends on issue #2 in this repository
depends: m1 - Depends on milestone 1 in this repository
depends: enhancedgi/i3 - Depends on issue #3 in the enhancedgi repository

Firstly, any milestone should inherit the highest priority of anything that depends on it, regardless of it's actual priority (unless it's priority is already higher than stuff that depends on it).

The algorithm is simple: a milestone or issue can only be started if all milestones and issues that it depends upon are already complete.

Ensure correct handling of de-selected repositories

If you don't include a repo but it does actually require a developer's time, will this be reflected, or will the project plan just assume that they don't need to do the additional things?