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
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
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
about 10 years ago
in Account settings
6
Unlikely to implement
Currently there's a create a related Idea in the action menu for a feature. I would love to have Create a Related Feature option so that when the feature is created, there's a relationship immediately established.
Guest
over 9 years ago
in Features
1
Unlikely to implement
Have users in Jira and Aha matched for comments, updates etc
I realise this is not Aha's fault, but if we put the issue here with more info, users will be more likely to go to Jira to vote for the issue there.
Currently whenever someone comments on an issue in Jira, in appears in Aha as a comment from the p...
It would be really useful to show the holidays in the GANTT chart, also with the possibility for the users to add custom days-off!I just realised that I was assigning tasks during Christmas Day....ooops. I understand it may be tricky to add all th...
Guest
about 9 years ago
in Features
3
Unlikely to implement
Include custom requirements fields in CSV upload into Aha
We have several teams who use the Aha CSV uploader to help cut down on manual entry time for recurring projects. It would be helpful if they were able to add custom requirements fields to the features uploader. As our company begins to scale, the ...
Guest
over 7 years ago
in Features
2
Unlikely to implement
Create ability for a feature to support multiple epics across workspaces. This will allow a single team that's working on a single feature that supports multiple epics across multiple teams. Currently we have multiple teams enabling a feature and ...
Steven Schafer
over 1 year ago
in Features
5
Unlikely to implement