Overview & Notes

Let's create some goals for nimble:

• Single Page Application: No full page reloads. At all. Ever. (except for the redirect at the end of Github's server OAuth flow during "login" - nothing I can do about this).
• Issues will be the focal-point of the app. Tiles seem like the most logical choice to represent issues. Nothing earth-shattering here.
• All API-provided filters will be available.
• Huboard provide a way to assign tasks to contributors by DnD of the contributor's Gravatar. That looks kind of cool, but it's not super-useful unless you have a small number of contributors and all of your contributors have easily distinguishable Gravatars. I'm thinking that contributor assignments are best left to the "edit issue" modal for now.
• It should be really easy to move issues between milestones.
• Columns are useful, and can be backed by tags with specific naming conventions.
• The ability to create a vertical priority list of issues is important. Furthermore, the issues should be aware of their priority not only among all other issues, but also among other issues in the milestone or column they the issue belongs to (or has belonged to at some point). Location can probably be stored in the issue description as a comment, which is what Huboard appears to do.
• Hooks should be used wherever possible to keep the data in the UI current.
• All aspects of an issue should be visible and editable via nimble. This includes basic fields selecting tags, the milestone, assignment, comments (edit, create, delete, view), description, title, and display of references such as commit messages and references from others issues.
• Github-style markdown support.
• There should be some native way to specify/view story points, calculate velocity, and auto-plan upcoming release cycles based on calculated velocity using priority-ordered items in the backlog. Story points could probably be stored in the issue descriptions as a comment. Total completed & attempted story points can be included & updated as comments in milestone descriptions. Velocity can be calculated on-the-fly by looking at milestones. Future release cycle planning based on velocity can be accomplished on-demand.
• Full-text search
• Move multiple issues between columns or milestones at once via drag & drop.
• Batch actions: contributor, milestone, column/tag, close.
• Reporting (graphs, lots of pretty graphs).
• Spiffy Github-like auto-complete of contributor names & issues.
• Work around glaring omissions in GitHub Issues, such as lack of a notification when an issue is assigned.