ADD A NEW IDEA

Application

Showing 7152 of 8642

Limit extensions to a set of users / group / team

I would like to be able to limit use of an extension to a set of users. For example, if I have an extension to deploy code to production, I would like to limit it so that only an ops team and team leads can trigger it.
Justin Weiss almost 3 years ago in Extensions 0 Future consideration

Ability to request to borrow a resource from a team

An initiative can be assigned to one of more teams, each with their own estimate. Sometimes we need a specialized skill set (eg. a front-end developer) to contribute to that initiative for a finite duration (ie. one week). We need an ability to re...
Mark Eaves almost 3 years ago in Capacity planning / Features 1 Future consideration

Allow each team to provide an independent set of tags on a feature

Looking at the tags field on a develop feature, it inherits all of the tags from my main roadmaps workspace. This isn't the behaviour I'd expect, I would expect a develop team to have its own unique set of tags of primary relevance to them. In pla...
Mark D almost 3 years ago in Application 1 Future consideration

Allow a feature to transition to different release phase when feature status changes

In order to make best use of multiple release phases I would like to be able to automate the moving of a feature from one phase to another when I update its status. For example a feature will be In design as a feature status and part of the Design...
Laura Phillips almost 3 years ago in Features 0 Future consideration

Extend the 'Lock fields based on Status of the record' to Custom Tables

We use Custom Tables in many workspaces to track dollar savings.Once a project reaches a certain status these committed savings should be locked. It would be a great enhancement to be able to do this with Aha!'s 'Lock based on Status' functionality.
Karla Johnson almost 3 years ago in Reports 0 Future consideration

Ability to restrict workspace owners to adding Viewer and Reviewer users only

It would be extremely beneficial to limit the control of adding paid seat user to administrators whilst still allowing workspace owners to add viewers and reviewers to their workspace. Where adding users is required to be restricted to administrat...
Rachel Fitton almost 3 years ago in Account settings 0 Future consideration

Allow responses to Ideas in a portal to come from a team, rather than a named individual

Allow the option to hide the name of an inddividual and replace it with a team oor company name
Keith Mantell almost 3 years ago in Ideas portal 1 Future consideration

Weblink to Strategy Components

Add the possibility to link individual Component a Strategy Model. The Component can be referenced from various parts of the platform, e.g. Description field of Releases, Goals, Features etc.
Guest almost 3 years ago in Strategy 1 Future consideration

Weblink to individual User Map Steps

Add the possibility to link individual steps of a User Map. The individual steps can be referenced from various parts of the platform, e.g. Description field of Releases, Strategic Models, etc.
Guest almost 3 years ago in User story map 0 Future consideration

Allow for "Create Related Idea" from Initiatives

Currently the "Create related idea" functionality is allowed for Epics and Features, but not Initiatives. However, Ideas can be promoted to Initiatives, Epics or Features. It is not clear why the relationship between Initiatives and Ideas is allow...
Mousa Mitwasi almost 3 years ago in Ideas 0 Future consideration