Account settings
Sort by:
Trending
Status:
Showing 640
2
VOTE
Global setting to turn off attachments
Our company works with sensitive data and we would like to globally shut off the ability to add attachments. In order to meet security requirements, we have quarterly auditing of attachments in addition to coaching users to insert an SSO protected...
0
Future consideration
1
VOTE
Product line prefix for all ideas of all product workspaces under it
Let's consider an example to understand it better: I have a product line called: "Line1" having a prefix as "L1" I have 2 product workspaces under the same product line, i.e., Product A with prefix as "PA" Product B with prefix as "PB" I have an i...
0
Future consideration
3
VOTE
Allow non-admin product owners to configure tags
Our teams are using tags heavily to add planning metadata to features. Over time, duplicate and mistyped tags are introduced which can cause confusion. At the moment, only those with admin access (one person within our organization) can clean up a...
0
Future consideration
1
VOTE
In-app requests for workspace roles
It would be great if users with access to workspace could submit a request within Aha Roadmaps for a different role to be assigned to them or for a role to be assigned to other users. This would streamline the process for admins to assign roles to...
0
Future consideration
1
VOTE
Search for statuses in workflows
My company has teams in different parts of the organization that use different workflows for epics & features, but many are different flavors of the same thing. It would be great to have a capability that allowed searching/filtering different ...
0
Future consideration
2
VOTE
Ability to assign multiple custom roles
It is currently only possible to assign a single custom role to a user. As an admin, I often define multiple distinct custom roles with very specific permissions. For example, a custom role to administer capacity planning and another custom role t...
0
Future consideration
3
VOTE
3
VOTE
Ability to create custom fields with context
When we create custom field in AHA we want the ability to create context for each product so that we can see only values which are relevant to a specific product. For example Team A, Team B and Team C are related to Product 1, we do not want to se...
0
Already exists
4
VOTE
permission-restricted release or feature status
We should be able to configure specific release statuses so that they're restricted, editable only by certain users or user groups.
We have a Program Management group which maintains an authoritative list of releases the product organization has c...
1
Unlikely to implement
2
VOTE
Assign Custom fields to a parent workspace
We have over 250+ custom fields being utilized by various workspaces. Because we cannot assign a custom field to a particular workspace all 250+ fields are visible in every filter in every workspace. If we could have the ability to define which wo...
4
Future consideration
© 2024 Aha! Labs Inc.•All rights reserved