Allow moving a feature to a completed release

Project Management is hard. I occasionally find tasks that were scheduled on a later release, but ended up getting completed, possibly due to a duplicate task, or the dev team pulled in a task from a future release.

This is a pain since I have no way to just say "This task is completed, and was shipped on release x.y.z". Jira allows this, and it's very handy when you need it. In Aha!, I have to jump through crazy hoops to do the same think.

Please add the ability to move a task to an already released "release" so it will be easier to clean up such items when you find them.
  • Chris Waters
  • Jan 8 2015
  • Unlikely to implement
  • Feb 5, 2016

    Admin Response

    As noted, features cannot be moved to shipped releases. As teams work on specific features, we would recommend moving them into the existing release for better tracking throughout the release process. This would allow you to see progress by the team over the course of the release.

    At this we do not have plans to make updates in this area based on community feedback and current priorities. We hope you can understand.

  • Attach files
  • Allison Lanager commented
    2 Jan 08:02pm

    In theory, completely understand and respect the point above.  On a normal basis I don't need to do this.   But every once in a while I find something that did actively ship with a release, with no way of adding it to the release. 


    This doesn't need to be supported everywhere.  Maybe from within the closed release I have an option to add a feature\etc from there as the override.


    But otherwise to get this item into the right place, I have to re-open the release, add the item to it, and close it again, and make sure I go back and pick the right shipped date, etc.  Then I get an e-mail notification that I shipped a release.


    I feel like this has even more potential for confusing people, and it changes the workflow dates because I have to navigate through the workflow.


    I generate a lot of reports tracking capacity, time logged, areas of development focus (IE: How much of our time was spent on customer commits this release), etc, so it's important all of the features wind up in the right release if that's where the team managed to fit it in.

  • Spencer commented
    16 Nov, 2017 06:48pm

    +1 - ran into this limitation this morning!