Skip to Main Content
ADD A NEW IDEA

FILTER BY CATEGORY

Jira

Showing 210 of 7169

Handle multiple FixVersions in JIRA

An Aha! feature can only be associated with a single release, however it is common for development teams to associate multiple fix versions with a issue in JIRA. Currently, the Aha! feature will overwrite the fix versions in JIRA if the fix v...
Danny Archer almost 7 years ago in Jira 12 Future consideration

Support for "Select list (cascading)" field type in JIRA

JIRA has a custom field type that supports cascading. This is a very useful field type that is currently not supported in Aha. Due to this, we cannot make the field required in JIRA and thus compliance drops off. The JIRA API supports this field s...
Guest almost 5 years ago in Jira 9 Future consideration

Synchronize logged time and remaining estimates from Jira back to advanced estimates

Using the Enterprise+ Capacity Planning for Teams feature, you can define an advanced estimate on a feature record and send it to the Jira. The total value of the advanced estimate is correctly reflected in Jira. However when the estimate is updat...
Mark Eaves almost 2 years ago in Capacity planning / Jira 0 Likely to implement

Jira sprint dates as feature end dates

With the Jira integration it is possible to pull through the Sprint name as a custom field into Aha Master Features/Features. It would be useful to be pull through the sprint finish date and apply that to all linked items within Aha. This would al...
John Biltcliffe about 3 years ago in Jira 4 Future consideration

Ability to map JIRA Team-field to a custom field in AHA

In integration 1,0 it was possible to map JIRA team field to a customfield in AHA, but in the new 2.0 integration that is't possible
Guest over 4 years ago in Jira 5 Future consideration

Enable Ideas to be sent to Jira as an issue type

We have all of our customers and internal stakeholders sending their enhancement requests to our Ideas Portal. Some of these are epic-sized, but most of them are small enhancements. We track small enhancements in Jira separate from our overall pro...
Guest over 2 years ago in Jira 1 Future consideration

Integrations 2.0: Add dependency link to connect records without natural relationships together

In integrations 1.0 if I mappedFeatures = StoryRequirement = TaskAha! would send the records to JIRA and create a "Relates to" dependency between the Story and the Task to visualize in JIRA that the two records should be related to each other.In 2...
Danny Archer over 4 years ago in Jira 3 Future consideration

JIRA: Detect default unit of time tracking

Aha! relies on time tracking in JIRA being set to the default value of minutes. If the value in JIRA has been altered to anything else, it throws time tracking estimates off. As of the 6.4.x version of the JIRA REST API a GET is available that ret...
Danny Archer almost 7 years ago in Jira 8 Future consideration

Show custom field names on integration errors

When there's an integration sync error with Jira on a custom field, Aha shows something like this: 'customfield_19011': Please fill out required fields The identifier 19011 has no meaning to us, as Aha doesn't expose a mapping of our custom field ...
Brian Trombley about 1 year ago in Jira 1 Future consideration

Add ability to map Custom Aha! Tables to Jira

Add the ability to map custom fields from custom tables in Aha! to Jira.
Guest about 5 years ago in Jira 3 Future consideration