When user logs out of Aha! the logout message should be sent to the IdP. If user logs out of IdP Aha! should process logout message and also logout user. This should be supported for both Aha! and for idea portals.
Chris Waters
almost 9 years ago
in Account settings
2
Unlikely to implement
Ability to set Feature Type when promoting an Idea
When I promote an Idea to a Feature, I would like to automatically set the Feature TYPE field based on information in the Idea record. The Idea CATEGORIES field is similar to the Feature TYPE, but multiple values can be selected for the CATEGORIES...
Roger Oliver
over 3 years ago
in Ideas
0
Future consideration
When using the JIRA Tempo plugin to track work time, it is useful to link issues to Accounts - for this the plugin exposes a custom field named Account. This field, formerly called Billing Key, is used among others in reporting, to decide which cu...
Guest
over 9 years ago
in Jira
8
Unlikely to implement
Synch story point estimates between Zenhub and Aha Epics (features)
We have linked Epics (Features) in Aha with Epics in Github Enterprise, and that is working fine. however we are using Zenhub to create story point estimates within Github, and would like to be able to reflect those estimates in Aha so we can do c...
Guest
over 5 years ago
in GitHub
4
Future consideration
When creating custom fields for ideas or features we need ability to select which user group has rights to edit it. We created a field named owners, with multiple select options from which a product owner can select several names of people that ow...
Guest
over 10 years ago
in Account settings
6
Unlikely to implement
In our organization we have a process that has specific phases w/ specific activities in each phase. It would be helpful to be able to create a schedule template w/ phases and the activities within that phase so we can easily standardize schedules...
Danielle Martinez
over 2 years ago
in Schedules
0
Future consideration
Requesting a change to Aha! Jira integration to allow for project level automation. Project level webhooks send payloads differently than system level payloads. If support for project level webhook payloads were added, we could enable multitudes o...
Guest
over 2 years ago
in Jira
0
Future consideration
The term "proxy vote" is not intuitive, which I believe is the reason some folks end up not using it. I would like to change it for "Voting on behalf of a client".
Anna Bittencourt
about 4 years ago
in Voting
4
Future consideration
When we review features with stakeholders, we need to consider and refine both the description (user problem) and the acceptance criteria (definition of done) before it can be approved. We also need the acceptance criteria to sync to an equivalent...
Brent Schumann
about 4 years ago
in Features
1
Future consideration
Allow workspace owner to grant additional permissions when access is given at the line level
What is the challenge? When users have been given access at a line level, workspace owners below that line cannot give them additional access (i.e. if someone is a reviewer at the line level a workspace owner in that line cannot make them a contri...
Julia Pence
11 months ago
in Account settings
0
Future consideration