A release is the date when a company is ready to deliver a new customer experience. All features that are part of a release should have a status which reflects that they are complete. This is because any unfinished features will be moved to another release of your choice.
Note: "Will not implement" will ship with the release since this status is a resolution.
You may choose to send an unfinished requirement to another feature, or make it a feature itself. Simply click on the requirement to expand it (or expand all requirements using the Expand all button). Then, under the Actions menu, choose Move to another feature or Convert to feature.
If you are using Aha! with an engineering integration and have already sent the requirement to that system, this action will not break the link between the engineering system and Aha!
The Ship date will be recorded as the release's "Released on date", so that reports can reference both the original and actual release dates for comparison purposes.
Once a release is shipped, you can't modify it. However, you can "unship" a release (in the Actions menu on the Releases page) if you need to edit it again. Shipped releases are hidden in a number of views, but in most places, you can still access a shipped release if needed. Shipped releases (and sometimes their features) can be seen or made visible on:
- Releases -> Overview - Add them via Filter
- Release -> Detail - Scroll left through previously shipped releases using the arrow at the top of your screen
- Features -> List - View shipped features
- Reports -> Features - Add them via Choose Releases
- Reports -> Pivot - Choose past dates
- Reports -> Portfolio - Visible by default
Shipped release notifications
Automated email notifications for shipped releases can be sent to watchers of the release by leaving the "Notify release watchers of the shipped release" box checked. Notifications will then be sent to watchers of the product that contains the release and the user who updates the release to "shipped" status.