Account settings
Sort by:
Trending
Status:
Showing 620
4
VOTE
Report on custom fields used in integrations, reports and roadmap views
Today you can identify which layouts and workspaces custom fields are actively used in. However, when looking to manage a large number of custom fields across a large organization, there is no way to determine which integrations are using that cus...
0
Future consideration
20
VOTE
Allow Requirement Dates to drive that roll up to a Feature to drive that Feature's start & due date.
We integrate with Jira Engineering work at the Requirement level and must see dates associated with Jira Stories as Requirements in Aha! Since addressing the Requirements / Jira User Stories make our Features a reality, we request that a setting b...
4
Unlikely to implement
6
VOTE
Standardize active user calculation
Aha! shows how many users are active in an account in two places: On the Billing page and in the CSV download of users on the Users page. For the Billing page, the number is calculated using the last login time, but for the CSV the report shows th...
0
Future consideration
1
VOTE
Add "date added" range filter to the user admin interface
What is the challenge? Need to quickly see and update user permissions based on when they were added (we use SSO - so user records are often created in waves when new teams onboard, but they still need permissions) What is the impact? Saves tons o...
0
Future consideration
1
VOTE
Auto disable Users when their Okta account is disabled
What is the challenge? When users leave the company and their Okta accounts are disable, their Aha user accounts remain active What is the impact? This impacts our available user license count in Aha Describe your idea Improve the Okta integration...
0
Future consideration
5
VOTE
Customize / Create New Record Link Relationship Types
In Aha! we can only create record link with the 6 default relationship types, while in Jira the new relationship types can be added and are customizable. https://www.aha.io/support/roadmaps/strategic-roadmaps/collaboration/create-record-links We n...
0
Future consideration
25
VOTE
Self Registration Capability for User Acess
We are a large organization with many users. We would like to share Aha! with interested individuals and that number could be hundreds or thousands. In order to alleviate that, the recommendation is to allow a self registration process that would ...
8
Unlikely to implement
7
VOTE
Follow custom workspace line terminology when viewing Roll up to workspace goals
When a workspace line references its parent, the naming of that parent should match the parent level, not the workspace level. By not reflecting the customized terminology we are introducing layers of confusion for the team members who don’t spend...
1
Future consideration
20
VOTE
Add more granular admin permission for configuring product lines
In order to maintain consistency across the product hierarchy, it is important to keep control over the naming and organization of product lines and products. In many cases some users should have administrator access to make customizations for the...
5
Unlikely to implement
7
VOTE
