How do you add/rename steps for Requirements Workflow

Thursday, June 26, 2014
Avatar
The requirements Workflow Steps appear to be fixed to a set of steps. Is there a way to create new steps similar to the way they can be created in the Incident Workflow? Is there a way to rename requirement steps similar to the way they can be renamed in the Incident Workflow?

Maybe this can't be done directly from the UI but done in the database?
5 Replies
Thursday, July 3, 2014
Avatar
inflectra.jimx
re: hstiteler Thursday, June 26, 2014
Hi Hugh

There is not currently a way to add/change requirement steps (unlike incidents). We are considering adding this feature in a future release, but for now it is not supported. Changing it directly in the database is not supported nor recommended either at present.

Regards
Jim
Thursday, September 11, 2014
Avatar
re: inflectra.jimx Thursday, July 3, 2014
Please add a big +1 (more like +200 users) for this functionality. We definitely need the ability to add/rename requirement workflow statuses.
Wednesday, December 31, 2014
Avatar
re: inflectra.jimx Thursday, July 3, 2014
I second that, being able to add new rq workflow steps would be a big help
Tuesday, June 2, 2015
Avatar
re: tmera Wednesday, December 31, 2014
thomas mera
I second that, being able to add new rq workflow steps would be a big help

 Is there any plans about this issue?

BR. Olli Mensio

Wednesday, July 17, 2024
Avatar
re: olli.mensio Tuesday, June 2, 2015

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.

Spira Helps You Deliver Quality Software, Faster and With Lower Risk

And if you have any questions, please email or call us at +1 (202) 558-6885

 

Statistics
  • Started: Thursday, June 26, 2014
  • Last Reply: Wednesday, July 17, 2024
  • Replies: 5
  • Views: 8561