Test Case Workflows

Hi Lisa

For incidents, documents and risks you can add workflow steps.

For requirements, test cases and tasks it is not possible to add steps. You can customize the workflow and add steps, but not add your own steps because their are automations and business rules that connect the steps in these artifacts.

Regards

David

Following up on this thread.

When we introduced product templates we made most of the statuses, all of the types and all of the priorities customizable.

We didn't make the following three artifact's statuses customizable:

• Test cases
• Requirements
• Tasks

This was because of the interconnections between them and the business rules that link them:

• When a release is assigned to a requirement, the status changes to Planned
• When all tasks are completed, the requirement status changes to Developed
• When all test cases are passed, the requirement status changes to Tested

Allowing these to be customizable and also have the linked business rules was deemed to be too complicated for the release in question.

Now with the advent of SpiraApps, it will be possible to allow customers to configure relationships between workflows more easily, so the longer-term plan is to reconsider making these customizable and use SpiraApps to integrate the flows. We are definitely aware of the need, and see it as a high priority going into 2025.

I support the request to add custom Statuses for requirements. Most of the customers do not need 

interconnections between them and the business rules that link them:

• When a release is assigned to a requirement, the status changes to Planned
• When all tasks are completed, the requirement status changes to Developed
• When all test cases are passed, the requirement status changes to Tested

But having a main process (flow of the requirements) customizable must have for sure.