Skip to Main Content
ADD A NEW IDEA

All ideas

Showing 8698 of 8698

Integrated icon or color on release column of board views to show integration linked

My users are expected to help keep their roadmap releases integrated to the tools of the engineering team (jira or Azure Devops). They need to link the release to the jira release or ADO iteration path, to keep roadmaps and scope alligned in both ...
Kevin Martin about 1 year ago in Integrations 0 Future consideration

provide option to share/pull configuration with/from roadmap in the Develop team configuration

As I add more Dev teams linked to a roadmap configuration, I wish for a configuration choice to rapidly match the workspace workflow and custom layouts between a linked roadmap and dev workspace. Ideally, I could go to either workspace configurati...
Kevin Martin about 1 year ago in Application 0 Future consideration

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

Approvals - Fixed Workflow

The Approval does not allow more than one person to approve – we wanted the reverse to have that one person can approve to move forward but we still want all people to have the option to approve for purposes of tracking. Once one of the two people...
Karla Johnson about 2 years ago in Application 0 Future consideration

Ability to black out dates in the date picker custom field

Our team is using the date picker for a "need by" date from our internal teams Idea requests. It would be ideal to be able to "black" out or only allow them to choose a date in the future and limit the request being requested and "needed" on the d...
Carolee Snarr over 3 years ago in Features 0 Future consideration

API access for Master Feature->Features and vice versa dependencies

Our organization often maps Master Features against Features as dependencies, and there is presently no way to do analytics on this data because the information is not available via API. Please expose.
Frank Siler over 4 years ago in Epic 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