My ideas: Jira
Sort by:
Popular
Status:
Future consideration
Showing 171
8
VOTE
Show required fields in integration mapping
When setting up an integration, it would be helpful to have a way to be prompted to map required fields in Jira. Currently, it is possible to create an integration that does not have field mappings for required fields in Jira. This causes the inte...
1
Future consideration
8
VOTE
Do not allow requirements to be mapped without a Links To relationship set
It is possible to create an integration where you have requirements mapped to a Jira record type, and where you have no Links To relationship established to a parent record in Aha! This results in import errors where requirements cannot be importe...
0
Future consideration
8
VOTE
Integrating with a specific Jira board
It would be helpful if we could use the Jira integration to send features to a specific board. We have several dev teams working within a single project, but they utilize different broads. We would like to send a feature to open a record is a spec...
1
Future consideration
8
VOTE
Urgent Jira Integration Needs: Resolution, Resolved Date & Percent complete
These are critical to the success of our organization wide integration efforts which are ramping up very soon. Set a resolution in Jira when record is closed in Aha When Jira issues are closed the user is required to set a resolution during the tr...
2
Future consideration
8
VOTE
Persistent filters for integrations and incoming product updates
Using JIRA integrations, I have an Aha product that spans several JIRA projects. To work with this I have set up an integration per project with a specified JQL filter. For example my filter could include "priority = high". Other products througho...
0
Future consideration
7
VOTE
Fix field population in Aha/Jira integrations to only rely on email address or other specific data
Today when the Aha/Jira integration runs it looks up users in Jira based on email, then failing to find a match it checks first name, then last name. Jira returns results for these and Aha will select the first return. The problem is that if we ha...
1
Future consideration
7
VOTE
Including Dependencies in Jira integration at requirements/story level
We have been really enjoying the newer ability to include dependencies for features in our Aha-Jira integration, but are running into the issue not getting the same level of transparency for the user stories - to combat this, we would like the abi...
0
Future consideration
7
VOTE
Flag Feature/Story as had been deleted from integration
While I understand the desire to never delete a feature or story either in Aha or the integration partner (Jira in my case). I would like to see a feature that flags the deleted item in Aha as being removed. This would allow me to manually review ...
1
Future consideration
7
VOTE
Allow child integrations to inherit the "run-as" user from an integration template
The following idea is for the JIRA integration, but could describe integrations to other development tools using a similar web hook mechanism.
The integration template functionality allows settings from a master template to be adopted by child int...
0
Future consideration
7
VOTE
Show comments added in JIRA as part of a state transition.
Currently, when a comment is add to a JIRA issue as part of a state transition, the comment is not shown in AHA.
This is a real issue for us since the Engineering team adds useful comments in JIRA when they move an issue between states. This means...
2
Future consideration