You draw the distinction between 3 types of users in an Ideas Portal, yet the visibility permissions only reference 2 of those types. Please provide one additional layer of visibility permission to limit ideas to Aha! users only. Internal users ca...
I'd also like to see it highlighted where things have changed since a benchmark on a release - which is a separate distinct issue. This needs to include all fields within Features. This is not achieved by inspection of each feature, my key stakeho...
Add Release (Schedule) Name to Instant Notifications
I've received requests from several Aha! users to include the Release (Schedule) name and Feature (Activity) name in all notifications. The Feature (Activity) name is included in instant notifications and the Workspace name is included in the dige...
In workflows, add the ability to limit setting a certain status to certain users.
In workflows, most of the time a status like "approved" is available. However, at the moment everybody can set this status, so it pretty useless.
If only certain users (e.g. with a certain role) could set the status to approved it suddenly gets v...
Guest
about 9 years ago
in Account settings
2
Unlikely to implement
It would be a positive addition if you provided an option to hide the timeline on a roadmap. We prefer to visualise roadmaps that are focused on goals/objectives/outcomes and not include any form of dates or timeline on the roadmap. The best I can...
Graeme Pratt
over 4 years ago
in Roadmaps
0
Future consideration
I can have Master Releases that span Products, but I can't review the collection of features against a single budget. This is in our case a software package that is integral to a hardware product release, and is also available as a Product in its ...
Guest
over 4 years ago
in Features
1
Future consideration
Include custom fields in API and Webhook information
When querying the API and when posting to a webhook endpoint custom fields should be included - this will increase the integration possibilities
Specifically I want to trigger a devops/CD workflow in another tool XLrelease and want to know which ...
Ann L
almost 7 years ago
in Integrations
0
Already exists
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 9 years ago
in Pivotal Tracker
7
Unlikely to implement