What is the challenge? |
Not able to move feature to next release |
What is the impact? |
Feature that have not been completed are shipped with the release |
Describe your idea |
When using a fixed workflow approval to ship a release, you should not be prevented from moving features to the next release |
This will be useful for me as currently we have to use a Fixed Workflow to limit which users can Ship a Release. But having a Fixed Workflow then means the "Ship Release" process no longer happens. I.E. the Complete release changing the status of done features to shipped or moving the feature to the next release.
https://www.aha.io/support/roadmaps/strategic-roadmaps/releases-and-schedules/releases-introduction#complete-a-release