Skip to Main Content
ADD A NEW IDEA

FILTER BY CATEGORY

Account settings

Showing 409 of 7271

Pass data in shared fields between objects through linked objects

We would like data to be passed using shared fields across objects the same way promoted objects work. Today, if a field (e.g UCMGID) exists with same API key in IDeas, Features, Epics etc, that data will be passed when the Idea is promoted. What ...
Karla Johnson 11 days ago in Account settings 0 Future consideration

Custom Field - Internal Name & Choice Lists Report Display

When creating reports with custom fields, there can be many fields within an account that have similar names that will display as field options. We use the internal name to help differentiate and allow the user to select the right field they are l...
Karla Johnson 11 days ago in Account settings 0 Future consideration

MS365 SSO feature

Hi, Adding the identity provider based on ms365 server could be a great idea.
Guest 4 months ago in Account settings 0 Future consideration

Apply workspace templates to lines

Often settings like layouts, terminology, and navigation for parent lines may be purposefully different than workspaces. It would be helpful to drive standards for lines by allowing templates to be applied at those hierarchy levels. A few examples...
Jeanette Resnikoff 4 months ago in Account settings 0 Future consideration

History on Scorecards

The All Activity page provides a great history log of changes made to Workspace level objects. However, it does not provide information on Account level objects, such as Scorecards. It would be helpful to know who makes modifications to scorecards...
Guest 16 days ago in Account settings 0 Future consideration

Allow deletion of types and other data while still in use

There are several places in Aha! where we disallow a user action because an object is in use. For example, users can't delete a custom type while records are using it. We already have an elegant solution in place for this when changing from one wo...
Bryan McElhinney 17 days ago in Account settings 0 Future consideration

Allow ability to limit valid values in Feature fields to only display relevant values for the workspace.

When defining features in a workspace, you should only need access to utilize valid values from selected workspaces. Each workspace owner defines and reports on their valid values very differently. When all valid values from every workspace are di...
Karla Johnson 9 months ago in Account settings 0 Future consideration

Automation: support setting a date field to a value relative to another date field

I wanted to create an automation to update the external release date to match the release date on a release when that changes. Arguably we should just do this automatically already... but I was hoping that Automation would solve the issue After se...
Todd Meyer over 2 years ago in Account settings 5 Future consideration

Customize the terminology of "Enter manually" that appears beside the progress bar

Allow customization of the "Enter Manually" wording for the progress bar selection.
Lance Hook 5 months ago in Account settings 0 Future consideration

Introduce Customization Owners

As a large organisation with several independent product verticals, we need the ability to lock down account-level customizations (e.g. layouts, custom fields, workflows) by owner (+ collaborators) so that we can retain adequate controls without l...
Joe Buehlmeyer 8 months ago in Account settings 0 Future consideration