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 ...

We have some customer systems that we need to sync data back from. These are generally tasks that are created in systems we integrate with (specifically Azure Dev Ops, with the Task record). We are an outsourced product management company, so we h...

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...

Who would benefit? All user What impact would it make? For Aha: Increase value proposition for Aha relative to other tools like whiteboarding tools and Atlassian Confluence For Aha customers: Better alignment with customers unique requirement mode...

As a user, I don't want to receive overdue emails multiple times for a to-do which did not get completed. Sometimes the to-do doesn't get done but the release still ships. In that case I don't need to do the to-do but I still get the emails for it...

Instead of building multiple workspaces for each business entity, we use the Category field to capture this information. However, your dynamic form only allows the conditional rules to be placed on the category. This won't work for us. This is wha...

As a Rally Admin, this wording can be be quite confusing. I've had to explain it several times to users. Suggestion: Instead of Excluding, "Included Child Updates" - box is automatically checked, so users can uncheck if excluding those updates.

Who would benefit? Any Aha customer with jira integration that uses a separate jira field that has version data as values to enter. In my jira project I use a different field (other than fix version) to track what release our features will release...

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...

The "Initiative" filter on the Feature List page treats all groups of initiatives as "equal". It would be really nice if it would display based on the initiative roll-up, and then automatically select all the 'child' initiatives when setting the f...