Lesson 3 · Project and automation

The project's GitHub tab and tasks moving with their pull requests.

Goal of this lessonTo link the project to its repository and let tasks move with their pull requests.

The task moves as its pull request movesBranch or draft PRWork startedPR opened for reviewIn reviewMerged into defaultDone
Applies when the project's automation is on. Tasks only move forward: a task moved ahead by hand is never pulled back.

Step by step

  1. Open the project's GitHub tab

    On the project form's GitHub tab choose the repositories. With Move Tasks with Pull Requests on, three stages are asked; an empty 'When Merged' marks the task Done instead.

    The project's GitHub tab123456
    1. The project's repositories.
    2. The automation switch: off, links are made but no task moves.
    3. When work starts: a branch or a draft PR appears.
    4. When in review: the PR is opened for review.
    5. When merged: the PR that closes the task is merged into the default branch.
    6. Set-up step by step: connection, read, permissions and webhook; what is missing and what to do.
Forward only
Automation never pulls a task back to an earlier stage. A task your team moved forward by hand stays there; a reopened task is not closed by an old PR event.

Check yourself

What if 'When Merged' is empty?
When the closing PR is merged the task is marked Done.
Which PR closes a task?
One that names the task in its branch or title, or says 'Fixes T163' in its body, merged into the default branch.