Skip to Main Content
ADD A NEW IDEA

Application

Showing 5116

Allow to define the scope of tags/choice list custom field values (account vs. workspace)

It should be possible to define whether the values of choice list and tags custom fields (predefined or editable) are shared at account level (current behavior) or limited to workspace level such that workspaces can share a configuration but have ...
Thierry Loones about 1 year ago in Account settings 0 Future consideration

automation rule capability to pull values from object changing and pass to linked object

I wish for an automation rule capability that can detect a change on one object (or a row of a custom table), then take action to assign a value to a linked object (or connected row of connected custom table) where that value comes from the object...
Kevin Martin about 1 year ago in Application 0 Future consideration

Provide custom terminology on the Aha! develop engineering work part of backlog

My users are bewildered by the term 'engineering' work in the right half of the Develop backlog space. I wish for a custom terminology alternative. If I had a custom terminology option, I could find words that make more sense to the users as work ...
Kevin Martin about 1 year ago in Application 0 Future consideration

Ability to hide record prefix

At the beginning of activities and initiatives, there is grey wording. For activities it numbers the tasks, for example, MARKETING-11. The prefix is used to create a permanent unique identifier to locate records throughout the database. However, o...
Guest about 1 year ago in Schedules 0 Future consideration

Release Details for Integrations

We have some workspaces with many (20+) integrations into Jira. When you open the release details "Integrations" section, there is no way to differentiate between the integrations. In our example, I can only see 20+ line items showing the same inf...
Jon DeLong about 2 years ago in Releases 0 Future consideration

Workflow View - Add Parking Lot View

From the Workflow view, can you add a filter or the ability to add the Feature Board Parking lot. This will help minimize the need to switch to the feature board and then back to kanban for prioritization.
Marina Reyna about 5 years ago in Features 0 Future consideration

Ability to bulk edit dependencies and other item relationships

We use AHA across multiple sub-businesses. Our sub-business relies on capabilities delivered by another sub-business. It'd be much more efficient to make sure dependencies are properly mapped if I could make multiple features depend on another fea...
Guest over 7 years ago in Features 0 Future consideration

Automation rule on dates should allow for ranges, today etc. vs. an exact date

When creating automation rules around dates, it would be helpful to have options that key off of the date vs. have direct hits on the date. For instance, when date field updates to TODAY, do action. When due date is Within 14 Days, do action. The ...
Jeff Broderick about 1 year ago in Account settings 1 Future consideration

Goal - Initiatives Tagged, customize table

Within a goal, the tagged initiatives populate in a table. It would allow for greater visibility if we could customize the columns that are in this table to quickly notate which development team is assigned the work, the domain it falls under, etc...
Blake Falanga about 1 year ago in Product 0 Future consideration

Make record ID's distinct for records shared with Develop team

When users are notified of Product features that are assigned to a Develop team, the notifications link the users to the Roadmaps board where it originated. On the reverse, Develop features that get assigned to a Roadmaps release, direct users to ...
Stephanie Lechner about 1 year ago in Features 0 Future consideration