ADD A NEW IDEA

All ideas

Showing 8935 of 8935

Restrict license allocation to paid seat groups, not accounts

It's ridiculous to have "paid seat groups" and allocate those licenses to other psg's within the account. Licenses limits should be observed strictly within each psg. I've lost seats for my group without my consent simply because they've over-allo...
Guest about 1 year ago in Account settings 0 Future consideration

Internal users should be able to 'Follow' Organizations they are interested in

As an Internal Aha Dashboards user, I should be able to ‘Follow’ the Organizations that I am interested in. When I follow an Organization, I should be automatically added as a Watcher for any objects (Ideas, Features) that are created by or tagged...
David Barber about 1 year ago in Ideas 1 Future consideration

The Jira integration should allow the sending of a release to Jira and properly map the feature types to Jira issue types.

Today, sending a release converts all the feature types to the default Jira issue type specified in the Jira integration mappings. This makes the release level integration useless if you manage different feature types in Aha (e.g. bug, defect, fea...
Andrew Sweet over 5 years ago in Jira 1 Future consideration

Option to disable "click to advance" presentation page

We now have ability to include hyperlinks in presentation page. And also, some views such as Dependency Report, when embedded into a presentation slide, the webpage is rendered with hyperlinks to the features/releases. That said, if we are not ex...
Katha K almost 5 years ago in Presentations 1 Future consideration

Include epics in parent date calculations

Currently releases and release phases can be calculated from the child phases and features. Epics should be included in the records that parent dates can be calculated from. For example, a release may only include epics (i.e. no feature records) a...
Jeanette Resnikoff about 3 years ago in  0 Future consideration

Ability to filter dependency types on the custom roadmap or add a colour to the icon for different dependency types

The addition of the releated section on custom roadmaps is useful. However, it would be useful to be able to control which dependencies are shown. For Example I have created a custom roadmap of features I want all of those features to be displayed...
Andrew Brooks about 3 years ago in Dependencies / Epic 0 Future consideration

Automation rules should be able to update a related goal's status

When creating an automation rule it is not currently possible to update a related goal's status. Goals are the only related record type for which you cannot update the status. In my example, I would like to update the goal status based on a change...
Kelly Sebes about 4 years ago in  1 Future consideration

Push notifications on mobile apps

it would be useful especially to get notified on a new assignment or due date approaching.
Guest over 5 years ago in Mobile 0 Future consideration

Coalesce common dependencies in the dependency map

Right now, I have a task which depends on several other tasks, and some ofthose depend on the same underlying tasks. An example of this would looklike: A / | \B | C \ | / D I would expect the dependency map view to draw a line between B&D as ...
Guest almost 8 years ago in Dependencies / Features 0 Unlikely to implement

Ability to Make Record Name Read Only

We want to make all Epic fields read only for Epics with 'Done' status, as it makes sense that done Epics should not be changed / edited anymore unless reopened. We applied a custom layout for 'Done' status in a workflow; however, it seems that 'N...
Hank Liu about 1 year ago in Epic 0 Future consideration