Share the list of value among different custom fields
We have some custom fields that are replicated for Epic, Feature and Requirement (e.g. Area Path for the integration with Azure DevOps). They have a long list of values we need to replicate and maintain three times instead of one. It would be perf...
Guest
about 4 years ago
in Account settings
0
Future consideration
We create a lot of very similar releases. I know that we can copy a previous release, however it would be better to create a release template that is comprehensive, and to select from that release template when creating a new release (launching a ...
Guest
about 6 years ago
in Releases
0
Already exists
I have a list of 50 idea references, which all would need the same action to be taken.
Currently I can add "Search idea" filter to the list view. With that I can filter the idea's by reference or name. But only with one reference or name.
It would...
Antti Toivonen
about 8 years ago
in Features
0
Unlikely to implement
Allow Custom Descriptions (Tool Tips) for Default Fields in Layouts
Aha allows the user to create a description (tool tip) for custom fields within a layout, but you can't add descriptions to default/native fields, like the "Type" field at the Feature level. Given that the Feature "Type" field is completely editab...
Zach M
about 2 years ago
in Features
0
Future consideration
Add ability to create epic / feature template based on agile user story best practices
Your template function doesn't allow us to create a template with multiple fields of specific information input when creating the epic and/or features. We follow a agile user story best practices and each of the story types have specific informati...
Patricia April
about 2 years ago
in Application
0
Future consideration
Assign an epic to two initiatives. We can have a piece of work, e.g. update master data, that can contribute to more than 1 initiative. I tested it out and if you add an epic from another initiative, it moves it rather than adds it
Guest
about 2 years ago
in Epic
0
Future consideration
Idea status automatic change when linking to an existing feature
If you link an idea to an existing feature the idea status should automatically change to "planned" like it does when you promote an idea to a new feature.
This creates manual processes and it can be confusing for the idea reviewers.
Guest
about 8 years ago
in Ideas
0
Unlikely to implement
The Ideas list view allows me to filter ideas by the date range a specific status change happened (eg. changed to 'Incoming' or changed to 'already exists') . I would like to be able to filter my list of ideas that had any status change in a given...
Only send Aha Feature Name to Jira Summary once - while not breaking Integration 2.0
My use case is the following: Product wants to shorten the Aha Feature Names so they look better in Aha's roadmap views.
On the other hand, I don’t want Aha to overwrite my more descriptive Summary on my Jira tickets.
How do I set up the integrati...
Guest
about 6 years ago
in Features
0
Future consideration