Thread

Skip Navigation LinksForums > SpiraTeam Forums > SpiraTeam Issues & Questi... > Release Active Flag?

Release Active Flag? RSS Feed

Tuesday, April 19, 2011
Is there a way to prevent incidents being assigned to a release that is no longer active?
3 Replies
Adam SAdam S
re: Mark Allen on Tuesday, April 19, 2011
Wednesday, April 20, 2011
Incidents cannot be assigned to an Inactive Release. They can only be listed as being detected in such Releases.
Matthew FerryMatthew Ferry
re: Adam S on Wednesday, April 20, 2011
Thursday, April 21, 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?
Adam SAdam S
re: Matthew Ferry on Thursday, April 21, 2011
Friday, April 22, 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.

Tagged
Statistics
  • Started: 4/19/2011
  • Last Reply: 4/22/2011
  • Replies: 3
  • Views: 589
Powered by KronoDesk v1.1.0.15 | © Copyright Inflectra Corporation 2011-2016 | Licensed to Inflectra Corporation.