Review your workflow
Review your workflow
The workflow settings specify when the work is started and when it's completed. It is used in calculating metrics such as lead or cycle time of issues and pull requests.
The workflow settings specify when the work is started and when it's completed. It is used in calculating metrics such as lead or cycle time of issues and pull requests.
The workflow settings specify when the work is started and when it's completed. It is used in calculating metrics such as lead or cycle time of issues and pull requests.
Guide contents:
Guide contents:
Map your GitHub worklow
When importing a GitHub Project as a data source, your board columns are automatically mapped to either Not started, In progress, or Done. This information is used when calculating the Timing metrics.
If the suggested mapping looks correct, you can accept it by clicking Looks good to me. To make changes, click Adjust mapping. The boxes become editable, and you can drag & drop items between them.
Not started = Work to be done
In progress = Work started but not completed
Done = Completed work
Consider your work done only when tasks are fully done, so map your testing/review/waiting states to In progress rather than Done. That provides you with a better picture of your cycle times, including all the reviews that need to be done before a task is complete.
When importing repositories (instead of Projects), the timing metrics are calculated as below:
Lead time starts when an issue is created
Cycle time starts when the issue is assigned to a person, or when pull request is opened
Lead & cycle time is stopped when the issue is closed, or the pull request merged
Map your GitHub worklow
When importing a GitHub Project as a data source, your board columns are automatically mapped to either Not started, In progress, or Done. This information is used when calculating the Timing metrics.
If the suggested mapping looks correct, you can accept it by clicking Looks good to me. To make changes, click Adjust mapping. The boxes become editable, and you can drag & drop items between them.
Not started = Work to be done
In progress = Work started but not completed
Done = Completed work
Consider your work done only when tasks are fully done, so map your testing/review/waiting states to In progress rather than Done. That provides you with a better picture of your cycle times, including all the reviews that need to be done before a task is complete.
When importing repositories (instead of Projects), the timing metrics are calculated as below:
Lead time starts when an issue is created
Cycle time starts when the issue is assigned to a person, or when pull request is opened
Lead & cycle time is stopped when the issue is closed, or the pull request merged
Accessing the workflow settings
You can access the workflow settings by selecting Data Mapping from the main menu.
When using GitHub projects, you may add new columns to your board. By default, new workflow states are automatically mapped to either Not started, In progress, or Done. Alternatively, you can force the mapping of new states by selecting one of the other options from the menu.
Accessing the workflow settings
You can access the workflow settings by selecting Data Mapping from the main menu.
When using GitHub projects, you may add new columns to your board. By default, new workflow states are automatically mapped to either Not started, In progress, or Done. Alternatively, you can force the mapping of new states by selecting one of the other options from the menu.