As part of the Tikal internal DevOps course, this is the session about issue tracking items as the center of the development processes

1. Issue-in-the-middle
Toward a better collaboration
Yoram Michaeli

2. Agenda
• Project
• Issue
• Issue-In-The-Middle

3. Demo project – Winter-Is-Coming

4. Demo application

5. Project lifecycle

6. Bug Task
Issue
Feature/
User story

7. Project issues
board
WIC-###

8. Winter-Is-Coming - version lifecycle

9. Issue & GIT
GIT tools
enables better
implementation
of the model

10. Issue branch
Each issue will have a dedicated GIT
branch for development (usually
called ‘feature branch’)

11. Local repository commit hook

12. Links everywhere
• Commits linked to issues
• Issue linked to commits
• Build linked to issues and commits
• Release notes linked to issues and commits

13. Smart commits

14. White/black lists
Issues - that failed build
or tests on branch - can’t
be merged to main
branch
Issues – that were not
been listed as approved -
can’t be merged to main
branch

15. Pre-receive hook
• Check that commits contains issue IDs
• Build and tests passed OK
• Issue not in black list or is in white list

16. Post-receive hook
• Builds triggering
• Notification sending
• Issue status change
• Pull request automatic creation

17. Pull request merge conditions
• Build passed build and tests
• Approved code review
• Commit contains issue ID
• Issue is allowed for merge and have a proper status

18. Release notes
Based on the change-set – compared to
last release – release notes is a list of
issues IDs with their titles

19. Split issue
Usually, when you fix a bug on a release-branch, you
want to fix it also on the main branch and even on
other release branches.
You can merge to whole branch or you can use cherry-
pick between branches.
In any case, this require a different issue for each
branch

20. Questions? Thanks!