Releases

When clicking the + button to add a new release, it only gives you a very limited number of inputs to create the item, which don't appear to be customisable. When creating a release card, you can determine which items are visible and layout, so th...

I want to use one set of terminology at the Product Line level and another set within its Products. ie, Initiatives at the Product Line level and Epics at the Product level. Allow me to set the terminology for all products in a product line's conf...

Many marketing teams use Aha! to create and manage their marketing campaigns and roadmaps. This use-case typically involves representing campaigns as Aha! Releases and generates many more releases than a software development use-case would (typica...

There are instances where we run into a situation that upon shipping a release, features that are not in done status will move to the next slated release in the workspace. This is not ideal, as features in one release may not relate to the other, ...

As a Product Manager, I want to be able to add a standard release cadence and if one of my releases gets delayed, the rest of the releases get pushed back as well. For instance, if we have standard 8-week release schedules and one gets delayed by ...

Currently the release date field is required. But usually when a release is first written up there is no realistic idea for when it might be delivered. For releases that are postponed or of lower priority, the initial entered dates which seemed so...

i have set the phases up with specific colours to help with identifying the different streams of work for a release; however, the 'view colours' options don't include custom colours, only 'status', 'assignee' and progress.

There are instances where multiple releases exist within the same product workspace that are separated intentionally for visual management. Creating a rollup release causes the children to inherit the parents name, but it would be useful for the c...

Currently when you duplicate a release there is no warning about the consequences of the duplication job (e.g. number of objects duplicated). As a relatively new user I ran into this when I recently duplicated a release, thinking that it would jus...

We have monthly releases configured. At the end of month, I move any open stories to the next month. The story reflects the new release, however, the associated JIRA ticket still shows the original release. To resolve, I have to go into the story,...