No release change on task

Thursday, December 4, 2014
Avatar
Hi,

we're using SpiraTeam 4.1.0.5. If I change the Release of an requirement, let's say from 5.1.0 to 5.2.0, and this requirement has some tasks, the tasks release does not change. Why is this so and how can I change this behaviour?

Thanks!
3 Replies
Monday, December 8, 2014
Avatar
re: Developer Thursday, December 4, 2014
Hi Johann,

By design, when updating the requirement release, its tasks' releases are updated automatically only if they are still in "Not Started" status. Does that explain what you are seeing?

Regards,
Elise
Tuesday, December 9, 2014
Avatar
re: inflectra.elise Monday, December 8, 2014
Hi,

Thanks. Yes, that's it. But I think this behaviour makes no sense. If I update a corresponding release, than it's relations has to be updated too. Currently the started tasks "hanging in the air" if I update the release. That's not helpful. Do you know what I mean?

Thanks a lot!
Friday, December 12, 2014
Avatar
re: Developer Tuesday, December 9, 2014
Hi Johann,

Yes, I think I know what you mean. There may be a better way to handle it. One idea is to add a "split task" function. It would break a partially-completed task into two tasks: one completed and one not started. Then when you move the requirement to another release, the "not started" task would move along with it.

Can you log a help desk ticket so that we can better understand and address your specific needs?

Thanks!
Elise
Statistics
  • Started: Thursday, December 4, 2014
  • Last Reply: Friday, December 12, 2014
  • Replies: 3
  • Views: 1581