We currently have no way for Rally to tell Aha that a feature is fully groomed. This would help considerably to give Product team visibility to the feature grooming status in AHA for PI Planning and priority alignment. Aha has a feature status of ...

This idea to suggest an enhancement the 'Trend' Report type to include an additional generated future trend line to forecast where the trend of existing data is headed. The screenshot below has a green dotted line to illustrate how the proposed fo...

We have a field on our epic cards called Integrations. It lists the ID# of the epid in ADO that our Epic in Aha is tied to. When I type a services id into my search field I do not find any results. If this were a searchable field in Aha I would ha...

Hi, I build and use software for more than 25 years. I use your software for 2 years now, and to be honest, i have never seen a software like yours. It is brilliant in its business use, it moves/change fast, its usage velocity is incredible thanks...

As more people use password management apps like 1Password, it's super annoying to not have a way to input both username (email) and password at the same time using the quick login button since you guys separate each field by a mouse click. I gues...

Sometime companies use customized templates with custom work item types. Currently the ADO integration only supports integration with the standard types like "initiatives", "features", "Requirements". Our template supports a custom type called "PI...

Personas within a single workspace can become unwieldy, especially for complex products that cater for a wide range of very different user groups and domains. It would be great to group personas within folders. Folders would also be useful to dist...

The drawer is often the main content you are interacting with on a page. I'd like to see the drawer become part of my browsers navigation state and history. Ideally, you could refresh a page with a drawer open and it would be stay open. You could ...

It is clear to me in many aspects of the UI consideration has not been given for working at scale. For example: Our tag list has grown to several thousand entries and yet I can only prune the list one entry at a time. Our product tree has over one...

When features all have estimates and dependencies and are assigned to phases, I’d like to be able to say “begin as soon as possible” and have all feature start dates be updated automatically within a phase, based on those estimates and dependencies.