Pull releases through with a project template.

Wednesday, January 27, 2016
Hi There,

We have been looking at best practices for dealing with requirements that we have decided are not feasible as currently we leave them as they are and it effects the requirement coverage when reporting on how well test cases are covering said requirements. Our idea is to set up a "Deferred Requirements" release to store each of these as we haven't been able to find a built in method for removing these from the reporting other than deleting them, which we do not want to do.

Is there any way we can set up a Deferred Requirements release in our Project Template that will be created when building a new project using this template to save us having to manually raise this release every time we create a new project?

Many Thanks,

1 Replies
Friday, January 29, 2016
re: bpatterson.consortium Wednesday, January 27, 2016
Hi Ben

Thanks for your question.

Assuming that you're running SpiraTest v4.2 or later, you should be able to move the Requirements to the 'Obsolete' status and then they are no longer counted for test coverage.


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


  • Started: Wednesday, January 27, 2016
  • Last Reply: Friday, January 29, 2016
  • Replies: 1
  • Views: 6257