Skip Navigation LinksHome Page > Forums > SpiraPlan Forums > SpiraPlan Issues & Questi... > Requirement Status
Is there any way I can change or custom the requirement status and workflow? I can change the workflow but cannot touch the predefined status of the requirements (Requested, Completed etc...). I want to change to something like Draft but couldn't see that in the template
Yep, cutomization of workflows:
is also needed for our company.
There are some reasons we don't allow requirement and test case statuses to be edited at present.
It is due to the automation available where changes to test case and task statuses automatically affect the requirements they are associated with. If we allow you to fully change the statuses, that automation will break.
David, thank you for your answer.
If you ask us between choosing automation and having custom names of the requirement's statuses, we choose having custom statuses (we have already switched automation of as all automatization is not really compliant: if a task was started, the requirement jumpes to "In Progress" status with passing obligatory status "Accepted", where it should be signed by PO ). So, anyway automation should be rewritten.
According to many threads in defferent Inflectra forums, I may expect that others vote for the same.
I would definitely rather have the ability to customize the status and workflow rather than the automation, which we have also turned off. I've tried using the statuses to mean things that make sense in our environment, but then they don't display on the planning boards correctly. Very frustrating.
David, see please an answer from bbernardin (whom I don't know by the way). He has the same views what is more important for Spira. We don't need automation but custom statses it is what is expected from all forums here. Look through different topics and forums.
When you say automation would break do you mean the Requirements workflow?
I was thinking about adding in a new requirement status directly into the database ( which would be outside of the requirements workflow) but would not want to risk impacting the existing requirement's workflow)