Release Active Flag?

Tuesday, April 19, 2011
Is there a way to prevent incidents being assigned to a release that is no longer active?
3 Replies
Wednesday, April 20, 2011
re: MarkAllen Tuesday, April 19, 2011
Incidents cannot be assigned to an Inactive Release. They can only be listed as being detected in such Releases.
Thursday, April 21, 2011
re: inflectra.david Wednesday, April 20, 2011
I know what Mark means. 

We have to use the "Release Detected In" field as a way of assigning an incident to be worked on in a given release. That seems to be what drives defect visibility within a release for the entire app. 

We use the incident structure for defects and defect management, which I think most customers also do. For example - we find a defect in the current production release and we need to "assign" that defect to the next release coming up in our pipeline so that we can address it.

Is there another way to assign an incident to a release?
Friday, April 22, 2011
re: mferry Thursday, April 21, 2011

You typically should use the Resolved in Release field to specify the release that the defect is planned to be addressed in. The Detected in Release is only meant to signify the release that the defect was found in.

I hope that clarifies things better.

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: Tuesday, April 19, 2011
  • Last Reply: Friday, April 22, 2011
  • Replies: 3
  • Views: 1872