Project Management: Create Issue workflow documentation.

[russellwjoel]

It would be useful to have a documented outline of a typical Git Issue work flow path,

This would help inform the use of Zenhub//Git issue tools as well as GaantLab includign: Labels Gaant time lines. recording effort (time) spent on each issue. (and each stage).

A work flow diagram would be an equally useful 'quick-reference tool'

---

example Create Issue -- Assign it X label (X?= To be estimated.. or Initial state) -- Assign meta label (which stays with ticket . -- bugfix, enhancement) -- Place it in . Y Zenhub Canban lane.

Review Issue in sprint plan meeting (or other review call). This happens every Z weeks. -- Remove X label -- assign to Zenhub lane . - Backlog

• Ready for work -- Give estimation -- Label

Add issue to work lane for current sprint -- assign a team member to work on issue -- give fixed estimate in sprint meeting

Issue worked on

• Branch created - referenced from issue in comment?
• Worked on by assignee.
• Time logged in the work log field on ticket. ??

Issue implementation complete

• Comment added on issue to reference branch and commit hash. (is there a better way to do this?)
• Label with ready for review.
• Move to QA review phase.
• Assign reviewer

Review

• Comments added on issue
• Passed to either Rework or Merge

Rework

• Assign to original implementer
• label: rework Work is conducted --> Passed back to reviewer. Repeat until Merge path is taken

Merge

• assign to original implementer
• label: ready to merge

• create pull request.

  Ticket moves to DONE

Release at end of sprint

                    Ticket moves to Closed 

[russellwjoel]

This seems relevant to implement given discussions within the team.

To include:

• Labeling overview -> when they are used.

• When to move the tickets into which lane -> I think it's best to just have PRs in the QA lane