Ability for a user to see what permissions they have
Our Aha! admin team frequently gets asked "Do I have a paid seat and which workspaces do I have edit permissions for". And so every time, someone from the admin team has to go take a look in the user admin area and report back. This causes an unne...
Steve Dagless
over 2 years ago
in Account settings
0
Future consideration
This is for the Strategic Initiative Four Quadrant Chart.
In a typical 4 quadrant chart there are two axis, I suggest using One Scorecard per Axis.
Example:
The Y Axis is Value and the Value Scorecard can have many contributing factors such ...
David Main
almost 8 years ago
in Account settings
1
Future consideration
This would allow a person to review if something changed on the configuration and what was changed.
The benefit is is something changed and a person is not aware, they do not add it back. Or if something was modified, we can find out why and reso...
Guest
almost 8 years ago
in Account settings
1
Unlikely to implement
When I add a custom field it would be helpful to be able to do one of the following:
add help text / description (this is how it works today)
add a link to help text (this is the request) - what we need users to enter is complicated and the "how ...
Sandy Goertemiller
almost 8 years ago
in Account settings
1
Already exists
Aha! permits the inclusion of custom logos at the account level. However, in the case of an account having multiple workspaces representing different product lines or subsidiary companies, it would be nice to have the ability to define custom logo...
Guest
almost 4 years ago
in Account settings
3
Future consideration
Engineering managers & team leads sit "in between" Aha! Roadmaps and Aha! Develop. They more than just team owner permissions, but not full workspace contributor permissions. Key use cases Team leads can provide initial estimates on features b...
Restrict visibility on initiative or feature based on their status
What is the challenge? The content of certain initiatives or functionalities must be shared with stakeholders for validation. However, we do not want these stakeholders to have access to all initiatives and features that are not yet in Validation ...
Terminology customizations should persist throughout all screens when cascaded from Account level
We have updated some terminology for all of our products to use “Feature” (instead of default Master Feature), “Epic” (instead of default Feature) and “Story” (instead of default Requirement).
Unfortunately, this update in terminology isn’t consis...
Kirstin Maurer
over 7 years ago
in Account settings
0
Already exists
Currently, it's difficult to determine which fields/content is included when using the Search feature of the Activity Log. It also seems like there's a lot of content not included when performing a keyword search. I don't see any online help conte...
Brian Cunningham
over 7 years ago
in Account settings
2
Future consideration