Default issues workflow
The issues workflow defines the path an issue takes from initial reporting to resolution. Issues are assigned to users who perform the work assigned to them. When the work is complete, the user enters an event to move the issue to the next state in the workflow. The issue Status field indicates the current state and assignment.
You can use the default issues workflow out of the box or customize it to support your process. The default workflow includes the following events.
| Event | Use to: |
|---|---|
| Assign | Assign issues to users. For example, you may need to assign issue to a support engineer for review and then the engineer can assign it to a developer to fix. |
| Estimate | Estimate the time needed to resolve issues or implement features. Typically, a project manager or team lead enters the estimated effort before assigning issues to developers to work on. After the estimate is entered, you can track the time it should take to complete a task. |
| Enter Work | Enter work you complete on issues to keep managers or team leads informed about your progress. |
| Comment | Add comments to issues to clarify information or add notes for other users. |
| Fix | Mark issues as fixed after they are resolved or the feature is implemented. The team member who fixed the issue or implemented the feature is generally responsible for entering the fix information. |
| Verify | Verify issues after they are fixed. If the verification fails, issues can be reassigned. |
| Force Close | Force close issues that do not follow the standard issue fix lifecycle, such as issues caused by third-party software. |
| Re-Open | Reopen closed issues if they reoccur and need to go through the fix process again. |
| Release Notes | Add release notes to issues to track the bug fixes and new features included in a release. |
Note: To add workflow events to issues, choose an option from the Workflow menu
