RELATED IDEAS
Ability to add automation to move a work item to a different release based upon a field
What is the challenge? |
There are times that certain records can move to a different release based upon the selection of a predefined choice field and do not require analysis and decisions. |
What is the impact? |
Inability to set up automation to do this causes non value add work for teams. |
Describe your idea |
Enable the ability to set automation to move an epic or feature to another release based upon a predefined choice field. |
© 2024 Aha! Labs Inc.•All rights reserved
I would expand the scope of this idea to just allow automations in relation to the Releases. It would be useful to be able to move Features, for instance, to the same release as the Epic it's assigned to. Currently, there are no automations related to adding or moving items in and out of a release.
We are working out a new process where we would have multiple parking lots for Features as they are create and move through requirements definition to being scoped and sized and ready for development. It would be great to be able to automatically move them to the next parking lot based on Feature status.