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 ...
Guest
over 7 years ago
in Features / Rally
0
Future consideration
Parent version mapped to 2 different releases - let user decide where to import
The same Jira version may be associated with releases from more than one Aha! workspace. This can happen when different products in Aha! are all being released together. When auto-import is enabled on the integrations and a new record is created i...
Mark Crowe
almost 5 years ago
in Jira
0
Future consideration
Better error handling when Trello card to move across boards
It is common practice for teams to have multiple Trello Boards. For example, in our organization, we have our "current development" board with Next Up, In Progress, Awaiting Validation, Completed ... and but like any product organization, you do n...
Angus Davis
almost 10 years ago
in Trello
0
Will not implement
Maybe this more of a product idea for Prezi team, but it would be very cool to be able to embed Aha! views and notebooks within a Prezi. Maybe there is already? The business value would be able to convey complex visual concepts (prezi) mixed with ...
Guest
over 7 years ago
in Wanted
0
Will not implement
Hello, I realize that we can add OneDrive integration on an individual basis. For our workspace, we do have individual OneDrive accounts but we also (and most importantly in a team environment with Agile) have a shared OneDrive account. With a sha...
Todd Materazzi
over 2 years ago
in Integrations
3
Future consideration
Automate service account password updates for TFS integrations
Right now we have a TFS integration configured with Aha which requires us to use an AD service account for TFS. This service account password needs to be manually added within Aha! however we have a policy that all our service accounts require pas...
We use the slack integration for PMs to know what each other is up to. It would be great to see the Product name as we change other details for each initiative. This makes it clear what product is changing.
Ken DeBlois
over 7 years ago
in Slack
0
Future consideration
Features should Inherit initiatives from Release & Master Release so all Pivotal stories are under the Epic after sending to PT (and the Epic is actually created)
When pushing a feature to Pivotal Tracker, a user can select a mapping that allows for initiatives to be mapped to epics. The only initiatives this works for are initiatives directly referenced by a Feature. Any initiatives referenced by the Relea...
Guest
about 10 years ago
in Pivotal Tracker
7
Unlikely to implement