The 3 ways to add automation I looked at were:
1) Automation built-in to project board, under workflows option, (more info here)
2) Custom actions built using Graph QL (info here)
3) Using actions/add-to-project action provided by github (repo)
Automation steps with relevant automation technique:
Issue added to project repo - > card added to project board (built-in workflow)
Issues gets assigned -> card moved to sprint backlog (custom actions)
Assignee creates a branch, submits draft pull request and works on issue -> card moves into 'In progress' (custom actions)
Assignee submits pull request -> issue card moves to done, and pull request added to project backlog (built-in workflows)
Review of pull request gets assigned -> moved to 'Sprint backlog' (custom actions )
Reviewer begins reviewing request -> moved to 'In progress' (custom actions - tbc)
Reviewer requests changes -> pull request moves to sprint backlog (custom actions- label 'changes requested' )
Assignee actions requests -> pull request moves to 'In progress' (custom actions- label 'changes requested' - tbc)
Assignee re-submits pull request -> (custom actions- label 'changes requested' - tbc)
Reviewer approves request and merges -> pull request moves to 'done' (built-in workflows)
Custom actions to be written:
1) Issue gets assigned to a person, move card from 'Project backlog' to 'Sprint backlog'
a. Pull request gets assigned to reviewer, card moves from 'Project backlog' to 'Sprint Backlog'
2) When assignee submits a draft pull request, card moved from 'Sprint backlog' to 'In Progress'
3) Reviewer requests changes, card moved from 'In Progress' to 'Sprint backlog', with additional label distinguishing second pull request review from the initial pull request
The 3 ways to add automation I looked at were: 1) Automation built-in to project board, under workflows option, (more info here) 2) Custom actions built using Graph QL (info here) 3) Using actions/add-to-project action provided by github (repo)
Automation steps with relevant automation technique: Issue added to project repo - > card added to project board (built-in workflow) Issues gets assigned -> card moved to sprint backlog (custom actions) Assignee creates a branch, submits draft pull request and works on issue -> card moves into 'In progress' (custom actions) Assignee submits pull request -> issue card moves to done, and pull request added to project backlog (built-in workflows) Review of pull request gets assigned -> moved to 'Sprint backlog' (custom actions ) Reviewer begins reviewing request -> moved to 'In progress' (custom actions - tbc) Reviewer requests changes -> pull request moves to sprint backlog (custom actions- label 'changes requested' ) Assignee actions requests -> pull request moves to 'In progress' (custom actions- label 'changes requested' - tbc) Assignee re-submits pull request -> (custom actions- label 'changes requested' - tbc) Reviewer approves request and merges -> pull request moves to 'done' (built-in workflows)
Custom actions to be written: 1) Issue gets assigned to a person, move card from 'Project backlog' to 'Sprint backlog' a. Pull request gets assigned to reviewer, card moves from 'Project backlog' to 'Sprint Backlog' 2) When assignee submits a draft pull request, card moved from 'Sprint backlog' to 'In Progress' 3) Reviewer requests changes, card moved from 'In Progress' to 'Sprint backlog', with additional label distinguishing second pull request review from the initial pull request