Within the JIRA integration, add the ability to hide options to 'send to' JIRA and only show the 'link with existing' options. This would be helpful for integrations that are designed/configured to be only 1 way (JIRA to Aha).
Kyle Kinder
over 2 years ago
in Jira
1
Future consideration
New "integration reference" custom field type to house read-only text reference to a field on other side of Jira (or other) integration
There are fields in Jira (and I imagine other integrated applications) that don't map cleanly to an Aha custom field type. I am proposing a new custom field type that is an always-readonly text field that can be mapped to any Jira field type, and ...
Gene Lewin
over 3 years ago
in Jira
0
Future consideration
As a user, I want to embed ideas within Confluence so the idea status is automatically updated as the feature is being developed. My use case is as follows: A customer I am working with ran into a weird edge case. I document the workaround in Conf...
Amelia Peklar
over 2 years ago
in Jira
0
Future consideration
Current workflow from what we have determined and as was suggested by Aha support: 1. A new idea/suggestion comes in from a customer, we promote a new requirement in an existing Feature. 2. It is promoted to a new requirement. 3. Within about 30 s...
Jon DeLong
over 3 years ago
in Jira
0
Future consideration
Map detailed estimates by initiative in Jira integration
What is the challenge? Right now, you cannot map detailed estimates by initiative. You can only map estimates for Epics, Features, and Requirements. What is the impact? When trying to estimate at a higher level and leveraging initiatives, you cann...
Kelly Fogus
about 1 year ago
in Jira
0
Future consideration
Copy integration mappings for records at the same hierarchy level
When configuring an integration between Aha! and a development tool, you decide what records in Aha! map to what records in the development tool and map the individual fields. It's common to have multiple record types in a development system at th...
Emily Yankush
over 2 years ago
in Jira
0
Future consideration
We need the Initiative ID available in JIRA integrations so they can be reference-able in other tool dashboards.
We use the Aha API to populate views in Tableau. The Initiative [API] ID is a crucial portion of making sure what we sync to JIRA from Aha and what we are looking at in Tableau which provides a combined view of both tools, is one and the same. I a...
Wen-Wen Lin
about 6 years ago
in Jira
1
Future consideration
We recently had to migrate JIRA tenant to another existing one (as the result of an acquisition). Whilst I was able to just change the server address and the integration URLs pointed to the correct location of the migrated issues, the board used f...
Jonathan Shaw
over 2 years ago
in Jira
0
Future consideration
Jira integrations : Add the capability to use filters instead of boards to set up integrations
What is the challenge? the boards only have tickets currently worked on , we want to load all tickets , so we can plan , this is because the team sometimes their create their own What is the impact? if you need to split a jira project with multipl...
Guest
about 1 year ago
in Jira
0
Future consideration