Managing Work Item Statuses and Transitions
Customize the statuses of different work item types, adjust their sequence, configure transitions, and set automated transition rules.
Prerequisites
A Scrum project is available, and you have permission to customize work items for the project.
Managing Epic Statuses and Transitions
- Configuring work item statuses
- Access the CodeArts Req homepage.
- Go to a Scrum project and choose .
- In the navigation pane, choose Statuses tab page is displayed by default.
Figure 1 Managing epic statuses
. The - Add, create, or delete statuses.
- Click Add Existing Status, select a status from the drop-down list, and click OK.
- Click Create Status. In the dialog box that is displayed, set the status name (for example, CustomStatus1), category (for example, Doing), and description, and click Add.
The new status is displayed in the current work item status list and on the Transitions tab page.
You can delete the added status as required.
- Press and hold on the left of a status name to rearrange the work item status by drag-and-drop.
- Configuring work item transitions
Configure the transitions between work item statuses. Then click the status of a work item on the work item list page to check the transition.
- Access the CodeArts Req homepage.
- Go to a Scrum project and choose .
- In the navigation pane, choose Transitions tab.
Figure 2 Epic status transitions
. Then click the - Select the allowed statuses and click Save.
- (Optional) After the configuration is complete, check the status of ceshi01 in the work item list.
Figure 3 Epic status transition
- Configuring automated status transition rules
Configure the handler options, default handler option, default comments, and whether comments are mandatory for work items transitioning to a specific status. In addition, specify the target status work items will transition to when a specific code message is committed. This configuration can improve your project efficiency.
- Specify a handler for work items in a specified status.
- Access the CodeArts Req homepage.
- Go to a Scrum project and choose .
- In the navigation pane, choose Automation tab. By default, Change Handler is selected.
Figure 4 Specifying handlers for epic statuses
. Click the - Click in the row of a target status (for example, ceshi01). Then configure the handler options, default handler option, default comments, and whether comments are mandatory for work items that transition to the cehsi01 status.
Figure 5 Configuring a status transition rule
- Click OK. The rule applies when work items transition to this status.
Figure 6 Epic status transition
- Specify a transition status for a code commit message
- Access the CodeArts Req homepage.
- Go to a Scrum project and choose .
- In the navigation pane, choose Automation tab, and select Change Status.
Figure 7 Specifying transition statuses for different code commit messages
. Click the - Toggle on or off the switch in the Apply column. Once the switch is toggled on, work items whose associated code commits contain the corresponding keyword in the commit message will automatically transition to the target status.
- Specify a handler for work items in a specified status.
Managing Feature Statuses and Transitions
- Configuring work item statuses
- Access the CodeArts Req homepage.
- Go to a Scrum project and choose .
- In the navigation pane, choose Statuses tab page is displayed by default.
Figure 8 Managing feature statuses
. The - Add, create, or delete statuses.
- Click Add Existing Status, select a status from the drop-down list, and click OK.
- Click Create Status. In the dialog box that is displayed, set the status name (for example, CustomStatus1), category (for example, Doing), and description, and click Add.
The new status is displayed in the current work item status list and on the Transitions tab page.
You can delete the added status as required.
- Press and hold on the left of a status name to rearrange the work item status by drag-and-drop.
- Configuring work item transitions
Configure the transitions between work item statuses. Then click the status of a work item on the work item list page to check the transition.
- Access the CodeArts Req homepage.
- Go to a Scrum project and choose .
- In the navigation pane, choose Transitions tab.
Figure 9 Feature status transitions
. Then click the - Select the allowed statuses and click Save.
- (Optional) After the configuration is complete, check the status of ceshi01 in the work item list.
Figure 10 Feature status transition
- Configuring automated status transition rules
Configure the handler options, default handler option, default comments, and whether comments are mandatory for work items transitioning to a specific status. In addition, specify the target status work items will transition to when a specific code message is committed. This configuration can improve your project efficiency.
- Specify a handler for work items in a specified status.
- Access the CodeArts Req homepage.
- Go to a Scrum project and choose .
- In the navigation pane, choose Automation tab. By default, Change Handler is selected.
Figure 11 Specifying handlers for feature statuses
. Click the - Click in the row of a target status (for example, ceshi01). Then configure the handler options, default handler option, default comments, and whether comments are mandatory for work items that transition to the cehsi01 status.
Figure 12 Configuring a status transition rule
- Click OK. The rule applies when work items transition to this status.
Figure 13 Feature status transition
- Specify a transition status for a code commit message
- Access the CodeArts Req homepage.
- Go to a Scrum project and choose .
- In the navigation pane, choose Automation tab, and select Change Status.
Figure 14 Specifying transition statuses for different code commit messages
. Click the - Toggle on or off the switch in the Apply column. Once the switch is toggled on, work items whose associated code commits contain the corresponding keyword in the commit message will automatically transition to the target status.
- Specify a handler for work items in a specified status.
Managing Story Statuses and Transitions
- Configuring work item statuses
- Access the CodeArts Req homepage.
- Go to a Scrum project and choose .
- In the navigation pane, choose Statuses tab page is displayed by default.
Figure 15 Managing story statuses
. The - Add, create, or delete statuses.
- Click Add Existing Status, select a status from the drop-down list, and click OK.
- Click Create Status. In the dialog box that is displayed, set the status name (for example, CustomStatus1), category (for example, Doing), and description, and click Add.
The new status is displayed in the current work item status list and on the Transitions tab page.
You can delete the added status as required.
- Press and hold on the left of a status name to rearrange the work item status by drag-and-drop.
- Configuring work item transitions
Configure the transitions between work item statuses. Then click the status of a work item on the work item list page to check the transition.
- Access the CodeArts Req homepage.
- Go to a Scrum project and choose .
- In the navigation pane, choose Transitions tab.
Figure 16 Story status transitions
. Then click the - Select the allowed statuses and click Save.
- (Optional) After the configuration is complete, check the status of ceshi01 in the work item list.
Figure 17 Story status transition
- Configuring automated status transition rules
Configure the handler options, default handler option, default comments, and whether comments are mandatory for work items transitioning to a specific status. In addition, specify the target status work items will transition to when a specific code message is committed. This configuration can improve your project efficiency.
- Specify a handler for work items in a specified status.
- Access the CodeArts Req homepage.
- Go to a Scrum project and choose .
- In the navigation pane, choose Automation tab. By default, Change Handler is selected.
Figure 18 Specifying handlers for story statuses
. Click the - Click in the row of a target status (for example, ceshi01). Then configure the handler options, default handler option, default comments, and whether comments are mandatory for work items that transition to the cehsi01 status.
Figure 19 Configuring a status transition rule
- Click OK. The rule applies when work items transition to this status.
Figure 20 Story status transition
- Specify a transition status for a code commit message
- Access the CodeArts Req homepage.
- Go to a Scrum project and choose .
- In the navigation pane, choose Automation tab, and select Change Status.
Figure 21 Specifying transition statuses for different code commit messages
. Click the - Toggle on or off the switch in the Apply column. Once the switch is toggled on, work items whose associated code commits contain the corresponding keyword in the commit message will automatically transition to the target status.
- Specify a handler for work items in a specified status.
Managing Task Statuses and Transitions
- Configuring work item statuses
- Access the CodeArts Req homepage.
- Go to a Scrum project and choose .
- In the navigation pane, choose Statuses tab page is displayed by default.
Figure 22 Managing task statuses
. The - Add, create, or delete statuses.
- Click Add Existing Status, select a status from the drop-down list, and click OK.
- Click Create Status. In the dialog box that is displayed, set the status name (for example, CustomStatus1), category (for example, Doing), and description, and click Add.
The new status is displayed in the current work item status list and on the Transitions tab page.
You can delete the added status as required.
- Press and hold on the left of a status name to rearrange the work item status by drag-and-drop.
- Configuring work item transitions
Configure the transitions between work item statuses. Then click the status of a work item on the work item list page to check the transition.
- Access the CodeArts Req homepage.
- Go to a Scrum project and choose .
- In the navigation pane, choose Transitions tab.
Figure 23 Task status transitions
. Then click the - Select the allowed statuses and click Save.
- (Optional) After the configuration is complete, check the status of ceshi01 in the work item list.
Figure 24 Task status transition
- Configuring automated status transition rules
Configure the handler options, default handler option, default comments, and whether comments are mandatory for work items transitioning to a specific status. In addition, specify the target status work items will transition to when a specific code message is committed. This configuration can improve your project efficiency.
- Specify a handler for work items in a specified status.
- Access the CodeArts Req homepage.
- Go to a Scrum project and choose .
- In the navigation pane, choose Automation tab. By default, Change Handler is selected.
Figure 25 Specifying handlers for task statuses
. Click the - Click in the row of a target status (for example, ceshi01). Then configure the handler options, default handler option, default comments, and whether comments are mandatory for work items that transition to the cehsi01 status.
Figure 26 Configuring a status transition rule
- Click OK. The rule applies when work items transition to this status.
Figure 27 Task status transition
- Specify a transition status for a code commit message
- Access the CodeArts Req homepage.
- Go to a Scrum project and choose .
- In the navigation pane, choose Automation tab, and select Change Status.
Figure 28 Specifying transition statuses for different code commit messages
. Click the - Toggle on or off the switch in the Apply column. Once the switch is toggled on, work items whose associated code commits contain the corresponding keyword in the commit message will automatically transition to the target status.
- Specify a handler for work items in a specified status.
Managing Bug Statuses and Transitions
- Configuring work item statuses
- Access the CodeArts Req homepage.
- Go to a Scrum project and choose .
- In the navigation pane, choose Statuses tab page is displayed by default.
Figure 29 Managing bug statuses
. The - Add, create, or delete statuses.
- Click Add Existing Status, select a status from the drop-down list, and click OK.
- Click Create Status. In the dialog box that is displayed, set the status name (for example, CustomStatus1), category (for example, Doing), and description, and click Add.
The new status is displayed in the current work item status list and on the Transitions tab page.
You can delete the added status as required.
- Press and hold on the left of a status name to rearrange the work item status by drag-and-drop.
- Configuring work item transitions
Configure the transitions between work item statuses. Then click the status of a work item on the work item list page to check the transition.
- Access the CodeArts Req homepage.
- Go to a Scrum project and choose .
- In the navigation pane, choose Transitions tab.
Figure 30 Bug status transitions
. Then click the - Select the allowed statuses and click Save.
- (Optional) After the configuration is complete, check the status of ceshi01 in the work item list.
Figure 31 Bug status transition
- Configuring automated status transition rules
Configure the handler options, default handler option, default comments, and whether comments are mandatory for work items transitioning to a specific status. In addition, specify the target status work items will transition to when a specific code message is committed. This configuration can improve your project efficiency.
- Specify a handler for work items in a specified status.
- Access the CodeArts Req homepage.
- Go to a Scrum project and choose .
- In the navigation pane, choose Automation tab. By default, Change Handler is selected.
Figure 32 Specifying handlers for bug statuses
. Click the - Click in the row of a target status (for example, ceshi01). Then configure the handler options, default handler option, default comments, and whether comments are mandatory for work items that transition to the cehsi01 status.
Figure 33 Configuring a status transition rule
- Click OK. The rule applies when work items transition to this status.
Figure 34 Bug status transition
- Specify a transition status for a code commit message
- Access the CodeArts Req homepage.
- Go to a Scrum project and choose .
- In the navigation pane, choose Automation tab, and select Change Status.
Figure 35 Specifying transition statuses for different code commit messages
. Click the - Toggle on or off the switch in the Apply column. Once the switch is toggled on, work items whose associated code commits contain the corresponding keyword in the commit message will automatically transition to the target status.
- Specify a handler for work items in a specified status.
- After the configuration is complete, click Save as Template in the upper right corner of the page. In the Save as Template dialog box, enter a template name and description, and click OK.
- This template can be used to create Scrum projects.
Figure 36 Creating a Scrum project
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot