ADD A NEW IDEA

All ideas

Showing 5973

Autocascade release dates

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 ...
Guest over 3 years ago in Releases 0 Future consideration

When deactivating a user provide links to access the integrations directly

Currently when deactivating a user, the warning message provides the list of integrations to see. It would be helpful if each of those were a clickable link to open the integration or a link to report to those integrations to view/open.
Chris Dauer over 1 year ago in  0 Future consideration

Ability to filter by 'inherited' in workspace settings report

When making changes to many workspaces at once - like a change of standards or following a reorg' - it's helpful only to report on workspaces where a setting is inherited. List reports include whether or not a setting is inherited but only as a te...
Steve Dagless over 1 year ago in Reports 0 Future consideration

Allow Jira-related fields to be included in automation rules

It would be helpful for fields like the Jira key or integration link to be available in automation rules. That would enable my team to create triggers that look at when an integration link is changed or is no longer available.
Katrina Purcell over 3 years ago in  0 Future consideration

Allow for null Release Date

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...
Brendan G over 3 years ago in Releases 0 Future consideration

Adding features from initiatives or whole initaitves in the story map would make life a lot easier

you can add existing records from a releawse or by feature, but adding entire iniatives worth of features is not possible. It would be helpful to be able to do that
Guest over 1 year ago in User story map 0 Future consideration

Handling Use Case of Features Tied to Company Initiatives

Use case: I have a “Test Company Initiative” parent initiative (company level) with child initiatives. Features are linked to those child initiatives. However, there may be one-off features that ALSO need to tie to the parent initiative because th...
Guest over 1 year ago in Reports 0 Future consideration

Sync Sprints betweeen Aha! and Rally

As product owners use Aha as the primary repository to develop and track their roadmap, they want to enhance their planning phase by improving the existing configuration between Aha and Rally. Currently, capabilities, features, and user stories ar...
Guest over 3 years ago in Rally 0 Future consideration

Handling Use Case of Initiatives with and Without Children

Use Case: I have initiatives at the company level. I also have initiative at the product line level that roll up to the company level initiatives. Not all company initiatives have "child" initiatives. There are multiple types of reports that displ...
Guest over 1 year ago in Reports 0 Future consideration

Allow child releases for a master release to retain unique names

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...
Ronnie Merkel over 3 years ago in Releases 0 Future consideration