Improved error message on incorrect JIRA record type link
Using the JIRA 2.0 integration, if you try to link to an existing record type that is not mapped in the integration config, the error message is very unhelpful. It just says "system error - contact Aha support if this persists" (or something like ...
Mat Wood
almost 6 years ago
in Jira
0
Future consideration
Calculate Epic Completion Based on JIRA Epic Completion
The options to calculate the completion of an epic in Aha is only based on user stories, but there are other items in JIRA that determine how complete an epic is. It would be helpful to have the progress bar completion automatically reflect whatev...
Rachelle S
almost 2 years ago
in Jira
0
Already exists
Provide options to prevent Sending over to Jira via integration if Status is not equal to a specific status
We need a way to prevent an end user from selecting the option in Integrations to Send to Jira unless the Status = Open. With it set to any other status, it causes Integration issues. We dont want to have to set up approvals to verify this. Just w...
Guest
almost 4 years ago
in Jira
1
Future consideration
API - support sending multiple parameters/values in search query
The API currently only accepts a single value search parameter. There is a requirement to be able to pass multiple parameters/values through the API. For example, execute a search through the API for features that contain 3 specific tag values.
Matt Case
almost 8 years ago
in Integrations
1
Will not implement
GitHub integration automatic log time upon linked issue completion
The intended use of GH integration is the following:
Create features in Aha
Push to GitHub as a handover of control to engineering
Updates in GitHub trigger status changed in Aha
This is a good start.
If control is passed to engineering to manag...
Guest
almost 8 years ago
in GitHub
2
Already exists
We are currently pushing Aha! tickets into JIRA. It would be helpful to have a link in Aha-created JIRA tickets that linked back to Aha (the same way Aha! has a ticket number and link to the JIRA ticket).
We have many users that have asked me for the ability to search for a Feature based on it's Jira Key. Currently the only way to do that using the Search box is for them to add the Jira Key to the Feature description, and they don't want to have to...
We're working on an integration where we'd like to know the plan name for the product. For example we'd like to distinguish whether the plan is Ideas Advanced or Ideas Essentials. On the similar lines we'd also like to know for Roadmaps the plan n...
Guest
about 4 years ago
in Wanted
1
Future consideration