Filter capabilities on the Integration Update Import screen
As one Product Owner of a very large product that has a lot of product owners, I would like more filter capabilities on the Integration Updates import screen so that I can only see items that pertain to my portion of the backlog. This request is s...
Slack integration - subscribe to release sub-record notifications
What is the challenge?
In the Slack app - I want to subscribe to a release and get notified when people add features in that release. Right now though that is not an option:
I want to also have the option to auto-subscribe to feature notificati...
Todd Meyer
6 months ago
in Slack
0
Future consideration
What is the challenge? In Salesforce if I merge an account into another account any ideas that were linked on the source account are transferred over to the target account. On the Aha! side, the link in the proxy vote to the account still points b...
Justin Waldorf
over 1 year ago
in Salesforce
0
Future consideration
Microsoft flow has over 175 triggers currently available. Examples include Zendesk - When an Item is created, Wunderlist - When a New task is created, Saleforce - When a record is created, Pivotal Tracker - When a story is created, etc. Having acc...
Guest
almost 8 years ago
in Integrations
0
Future consideration
Currently, as far as I am aware, the only way to use Components from Jira is to add a custom field in Aha! and map them. This works OK, however if a new component is added in Jira you have to manually add it to Aha! as an option to select. Please ...
Guest
over 2 years ago
in Jira
0
Future consideration
Ability to select only one user from the "User Field" custom field
Currently the "User Field" (custom field) in Aha! allows you to select one or more Aha! users.
It would be useful to have a "User Field" whereby a user can only select one user. This is important for us, as one of our User Fields sycnhronises wi...
Allow the JIRA integration to support mapping to more than one JIRA issue type and in Aha provide the ability to select the JIRA issue type to sync with
We use Aha for both Feature Requests and Defects and need to be able to designate if the JIRA issue type is an Epic, Story or Bug when linking to JIRA.
Kevin Konishi
over 9 years ago
in Jira
11
Already exists
Who would benefit? All the teams who are using aha and Gitlab setup for their SAFe ways of working What impact would it make? Streamlined and logical grouping of features which are created in aha and synced to Gitlab How should it work? Group leve...
Anusha Huddar
about 2 years ago
in Features / Integrations
1
Future consideration
What is the challenge?
As a system administrator, I need to have a quick and comprehensive view of all the different integrations to help me troubleshoot and support the environment
What is the impact?
It takes time and effort to manually ...
Guest
7 months ago
in Integrations
0
Future consideration