Record successful updates in Aha! from Jira "update records" action
What is the challenge? Currently, there are log events for successful updates made from Jira when using the "Update Records" action What is the impact? Users have no way of knowing which records were successfully updated and what fields were chang...
Stephanie Lechner
5 months ago
in Jira
0
Future consideration
What is the challenge? When referencing object in chat with team-mates, I have to copy the URL link and then modify to include object name (feature name, release name, etc.). What is the impact? If I don't do that, my team-mates must open the link...
Lukas Slavicek
7 months ago
in Application
5
Future consideration
Who would benefit? everyone What impact would it make? limits information leakage and information misuse to parts of the organization who don't need to see in progress epic development before it's put in an official release How should it work? wit...
paul raisanen
10 months ago
in Account settings
0
Future consideration
Copying an epic should also copy the associated features
Currently, if I want to copy a Master Feature, I must copy the Master Feature, then copy each associated Feature and map them to the Master Feature. This is time consuming and doesn't make a lot of sense.
doug evans
almost 6 years ago
in Epic
8
Future consideration
It would be very useful to be able to set read-only permissions for some fields (either standard or custom fields) based on permissions, or - even better - permission groups. In fact we have some fields on Features and Ideas that should be maintai...
Nicola Rolando
over 1 year ago
in Account settings
0
Future consideration
Allow Release Date (internal) and Release End date (date range) to sync
Who would benefit? The Release date (internal) drives many of the OOTB reporting functionality in Aha! so it must be maintained and accurate for reporting to be accurate. For many teams, the end date of the release and the Release date (internal) ...
Bonnie Trei
about 1 year ago
in Releases
1
Future consideration
Make the standard tags field mappable for requirements
Both epics and features have the standard tags field mappable when setting up an integration. Requirements now have a standard tags field added to the record but it is not available in the mappings. It currently requires a custom field be created ...
Justin Waldorf
over 2 years ago
in Integrations
3
Future consideration
The Prioritization view for ideas and features provides the ability to sort the main list by the Score. It would be helpful to sort by any of the columns displayed in the view.