PINNED
Chrome extension to capture feedback from anywhere
What is the challenge? We work in many applications and Aha! can not build custom integrations for all of them. This makes it very hard to users of those applications to capture feedback and store it all in Aha! ideas. What is the impact? This res...
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
almost 3 years ago
in Jira
0
Future consideration
Allow automatic imports of child records when parent records exist in a different workspace
What is the challenge? Currently, for Jira integrations, when you have parent/child records in Jira that span multiple Jira projects connected to multiple Aha! workspaces, all child records created will need to be manually approved as an integrati...
Stephanie Lechner
12 months ago
in Jira
0
Future consideration
What is the challenge? We use checkboxes for our Acceptance Criteria (AC). Sometimes, it makes sense to add additional detailed ACs under a bigger AC. We use an indent for this, however, after Jira sync, these indents are removed. What is the impa...
Manuel Froehlich
6 months ago
in Jira
0
Future consideration
Ability to create JIRA integration thorough Aha API
We have teams with several projects and creating it through templates is not practically scalable, hence require an API to create JIRA integration manually
Guest
about 8 years ago
in Jira
3
Future consideration
Rally integration - Create and update dependency relationships between features as part of two-way integration
When a feature is sent to Rally, also create predecessor and successor links according to feature links which exist in Aha! Changes to predecessor and successor links in Rally should create or delete feature links in Aha!
Matt Case
about 9 years ago
in Dependencies / Rally
2
Future consideration
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
almost 2 years ago
in Features / Integrations
1
Future consideration
The API pages the data it returns, and the pages are limited to a maximum of 200 records. In scenarios where it isn't possible to programmatically iterate through the pages, such as reporting & (Power)BI, it would be incredibly useful to be ab...
Daniel McGrath
almost 7 years ago
in Integrations
1
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
Removing the link between an Aha Feature and a Jira Epic should clear all fields included in the sync.
What is the challenge? When a Feature in Aha! is unlinked from its corresponding Epic in Jira, fields that were previously synced—such as the Aha! URL—remain populated in Jira. This creates a false impression that the records are still connected a...
Brittani Carmandi-Weber
6 months ago
in Integrations
0
Future consideration
Integration with Smartsheet - Indentation Mapping (Task Name)
What is the challenge? When establishing the integration Smartsheet with Aha!, the integration is very basic. It only allows us to map the information in Smartsheet to one type of item in Aha! (like Releases, Epics, Features ), and it only pulls i...
Albert Pivonka
6 months ago
in Integrations
0
Future consideration