Feature History Changed to show Story History too - Needs a filter to filter to only feature
The Feature History has changed to also show Story/requirement History. This makes it hard to find the history of the feature or single level you are looking at. History needs a filter to filter to only 1 level and not the children levels.
Steve Podzamsky
almost 2 years ago
in Features
0
Future consideration
We need to link Aha! Roadmap items to other items in Sparx EA (OSLC compliant) using ArchiMate 3.1 and an OSLC connector for Aha! will enable us to do that. This connector will also enable us to link Sparx EA ArchiMate 3.1 model elements such as s...
Guest
over 3 years ago
in Wanted
0
Future consideration
New section under Strategy or Info for definitions/product functions.
Our Product has multiple functions/modules. With each module there are some terminologies and concepts that need to be defined. I can use notes to create a document but that that can get messy really quick. I see this area working similar to how P...
Chris Eichermüller
over 3 years ago
in Strategy
0
Future consideration
Anyone with customization permissions can modify the Default workflows, scorecards, time frames, etc. Without removing the option to set new default, why not blocking the default from being modified? this will allow an encourage users with the rig...
Guest
over 3 years ago
in Application
0
Future consideration
Don't automatically open links in notes/descriptions in a new tab
When you try to open a link from a note/description in a new tab, some javascript automatically opens the link in a new tab and changes the focus to it. Opening a link in a new tab should be done in the background, like when done with the middle m...
Michel Billard
over 3 years ago
in Notes
0
Future consideration
Allow each team to provide an independent set of tags on a feature
Looking at the tags field on a develop feature, it inherits all of the tags from my main roadmaps workspace. This isn't the behaviour I'd expect, I would expect a develop team to have its own unique set of tags of primary relevance to them. In pla...
Extend the 'Lock fields based on Status of the record' to Custom Tables
We use Custom Tables in many workspaces to track dollar savings.Once a project reaches a certain status these committed savings should be locked. It would be a great enhancement to be able to do this with Aha!'s 'Lock based on Status' functionality.
Karla Johnson
over 3 years ago
in Reports
0
Future consideration
Add the possibility to link individual Component a Strategy Model. The Component can be referenced from various parts of the platform, e.g. Description field of Releases, Goals, Features etc.
Guest
over 3 years ago
in Strategy
1
Future consideration
Ability to aggreate work done value from both feature and requirements
Dear aha, in our scenario when AHA is synced with JIRA with time tracking attributes, we come into a problem with showing the complete work done on the feature when:
1. there is a time log in JIRA on epic (synced to feature)
2. there is a time log...
Daniel Pokrývka
over 5 years ago
in Jira
2
Future consideration