Skip Navigation LinksHome Page > Forums > SpiraTeam Forums > SpiraTeam Issues & Questi... > 'Developed' Requirement s...
I have created a number of requirements for a project in v5.4 and I would like to use the complete aspect of the requirements workflow for progress tracking and reporting.
I can see that tasks have multiple different types, including Development and Testing.
I'd like to understand why it is not possible to mark a requirement as Developed and still have Testing tasks which are not complete. The current behaviour means that the Developed state is not available unless I remove any unfinished tasks regardless of whether they are Development types or not. If I create tasks and mark them as Testing types, then the Requirement Status field will not move past In Progress
This seems to be broken. I expect to be able to report on the progress of requirements to each state that is available e.g. where a requirement has been developed but not tested. Currently I can only see that it is In Progress.
Is there no integration or mapping between task types and requirement statuses? If not, this essentially makes the Developed and Tested statuses obsolete.
The Tasks connected to Requirements are meant to be used for development tasks, so when all tasks are done, the Requirements shifts status to 'Developed'. When all the test cases are Passed, the requirement goes to 'Tested'. That is by design, and is intentional.
You can turn off this feature, so that all changes to the requirement status have to be explicitly done by the user. Just go to Administration > Planning Options and uncheck the options.
Thanks, that's good to know. I'll use this approach going forward.