Inflectra Customer Forums: No release change on task (Thread)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! en-US(C) Copyright 2006-2026 Inflectra Corporation.support@inflectra.com/Computers/Software/Project_Management//Computers/Software/Quality_Assurance/KronoDesksupport@inflectra.comhttp://www.inflectra.com/kronodesk/forums/threads120/Support/Forum/spirateam/issues-questions/1092.aspxthreadId=1092Johann Reisner (johann.reisner@kathrein.de)taskNo release change on taskHi, 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! Thu, 04 Dec 2014 14:15:31 -05002014-12-12T16:55:03-05:00/Support/Forum/spirateam/issues-questions/1092.aspxmessageId=1954Kat A (elise.brooks@inflectra.com) Hi Johann, By design, when updating the requirement release, its tasks' releases are update 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 Mon, 08 Dec 2014 18:08:07 -05002014-12-08T18:08:07-05:00/Support/Forum/spirateam/issues-questions/1092.aspx#reply1954messageId=1959Johann Reisner (johann.reisner@kathrein.de)Hi, Thanks. Yes, that's it. But I think this behaviour makes no sense. If I update a corresponding 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! Tue, 09 Dec 2014 06:38:24 -05002014-12-09T06:38:24-05:00/Support/Forum/spirateam/issues-questions/1092.aspx#reply1959messageId=1970Kat A (elise.brooks@inflectra.com) Hi Johann, Yes, I think I know what you mean. There may be a better way to handle it. One i 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 Fri, 12 Dec 2014 16:55:03 -05002014-12-12T16:55:03-05:00/Support/Forum/spirateam/issues-questions/1092.aspx#reply1970