Adding og renaming Requirement steps in workflow

Hi Karina

It is not currently possible to rename the requirement steps (only the incident steps). It is planned to be possible in the future once we add project template schemes.

Regards

Jim

Any updates on this? I found it requested in other forum entries from 2014, that's 6 years ago! And I don't even see it on the roadmap.

The currently defined steps are highly unsuitable for our workflow, which - in my opinion - is nothing uncommon at all. We need two separate review steps, first an internal review and second a review by the customer. To achieve this, we must abuse the existing steps which are a complete misnomer.

Yep, cutomization of workflows:

• Custom status names everywhere adding more/deleting existing,
• Custom order in filter drop-down on the list view
• Custom order on the Board

is also needed for our company.

Hello,
adding or renaming Requirement steps in workflow - Is this possible and how?
Best,
K.

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.