What is the challenge? Users are continuing to add new scope to an already-scoped and prioritised feedback by posting comments to the Aha! Idea that was already promoted How would you solve it? Restrict comments based on whether an Aha! Idea was a...
Guest
8 months ago
in Ideas
0
Future consideration
Control which fields a Develop user can update in a record in a Roadmaps workspace
Currently when an Aha! Roadmaps record is assigned to a Develop team that gives anyone with contributor permissions in the Develop team access to edit any field on the record (even those in the Roadmaps layout). I'd like a way to control this more...
When you create Pivot you would like to have totals per groups and be able to expand 2nd level columns to see further detail. If I have a PivotTable which is showing information on Epic Level, I would like to expand this column so that I can see t...
Christophe Bucheli
over 2 years ago
in Reports
0
Future consideration
Workspaces allow users to update/change the name AND the prefix. Similar for a Team I would like to change the prefix of the team. right now the only work around is to delete the team and rebuild everything.
Currently trying to search for any features created with no integration Name / Jira Key. Being able to search for 'Is Blank' on no Integration Name will allow me to build the report I need.
Paven Bains
over 2 years ago
in Reports
0
Future consideration
Include "Comments" when exporting a single feature
It would be great to have an option when exporting a single feature to have it include the comments. I state as an option because there are instances when the comments are not necessary but for others it is quite necessary.
Guest
over 7 years ago
in Features
3
Will not implement
Add internal field name to CSV exports to make importing simpler
It would be super helpful if CSV exports of lists were given a second header row to include the internal field name in addition to the friendly name for each column which is exported right now.
This would be really useful for those wishing to expo...
Guest
about 6 years ago
in Features
0
Future consideration
to control the amount of information that flows from JIRA to Aha I tend to create the Feature first in Aha and then link it with the corresponding Epic in JIRA. Next i import the stories associated with the Epic by going on the integration -> I...
Markus Gujer
about 6 years ago
in Features
2
Future consideration
We want to make all Epic fields read only for Epics with 'Done' status, as it makes sense that done Epics should not be changed / edited anymore unless reopened. We applied a custom layout for 'Done' status in a workflow; however, it seems that 'N...
Hank Liu
over 1 year ago
in Epic
0
Future consideration
Our companies uses a few custom fields as part of our features. All of the custom fields that we use are notes. Enabling note-type custom fields to be bulk edited would be extremely useful.
Guest
over 5 years ago
in Features
1
Future consideration