Skip to Main Content
ADD A NEW IDEA

All ideas

Showing 8941

Support bi-directional flow of data when mapping Aha! releases to Jira sprints as a field mapping for features

Use case: Aha! releases are mapped to Jira sprints as a field mapping under features. Currently this mapping is only supported in one direction, Aha! to Jira. It would be helpful if this mapping supported the flow of data in both directions.
Dale Potter almost 4 years ago in Jira 0 Future consideration

Adminstering Users - Need an extra column on the user export

I think an additional column is needed on the export to indicate if the user has been disabled or not. I’m seeing my user export list grow, but the CSV doesn’t readily show you if a user has been deactivated (their original permissions stay reside...
Joe Carpenter almost 8 years ago in Account settings 0 Already exists

Allow to set custom card layouts on a per role basis

Different roles need different details to be visible at a glance. Managers need more details than viewers. Allowing different default customized layouts per role would be helpful to keep cards as clean and focused as possible for viewers while bei...
Guest almost 2 years ago in Epic 0 Future consideration

Clearer indication of the data hierarchy when creating report queries

On the list, pivot, chart and custom roadmap query builder, the lines showing the relationships between records in the hierarchy are so faint that users rarely register them. This makes it hard for new users to see or understand the significance o...
Steve Dagless almost 2 years ago in Reports 0 Future consideration

Allow bulk handling from the prioritisation view

I am running a prioritisation camp with the business, and we have just prioritised a large number of items (this view is awesome btw...) Now I need to tag all the items we have covered so we can filter them out of future sessions - but - there is ...
Guest almost 2 years ago in Features 0 Future consideration

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...
Siddharth Bhojnagarwala almost 2 years ago in Account settings 0 Future consideration

Metadata_url for SAML should support fetching certificate information dynamically

In environments where certificates are rotated automatically every few months (Azure AD), the current strategy of fetching the metadata once and then saving it as manual settings will require refreshing it whenever the certificate is rotated.Metad...
Austin Merritt almost 8 years ago in  1 Will not implement

Import from CSV to all Products

I imported our data into the AHA trial. Then I organized my initiatives into a product hierarchy. Then I realized that my start and end dates were in the wrong format. Start date of 4/1/2019 went into AHA as start date of 1/4/2019. My fault. Howev...
Guest almost 6 years ago in Application 1 Future consideration

User story map should be renamed user journey map

to avoid confusion with user stories.
Carl Veillette almost 2 years ago in User story map 0 Future consideration

Enable the Drawer and Details layouts to be different

Add flexibility to modify the Details layout and Drawer layout separately. At the moment, when shifting the fields up and down on the drawer display, the same top-down list is applied on both views.
Mark Slykhouse almost 4 years ago in Features 0 Future consideration