My ideas: Jira

The new Epic/Parent link field for Jira is only supporting for NextGen projects. Classic projects need to be supported as well.

What is the challenge? If I am using an integration template to manage multiple Jira projects which can have parent/child records spanning multiple Aha! Workspaces (many to many relationship), If I add a child record from one Jira project to an in...

We have JIRA and Aha today and the tools are integrated as follows: Aha feature - JIRA Epic Aha requirement - JIRA story NA - JIRA sub-task For some reasons, I had to delete the integration with JIRA for a specific product line from Aha an...

Would like to be able to view the sprint a feature is currently assigned to in JIRA. It looks like we have most of the other fields available for mapping but that one isn't available. I get a ton of questions about when a feature is scheduled to b...

If you assign a JIRA issue to be unassigned, the assignee is not reflected in Aha! correctly which causes the next Aha! update to overwrite the unassigned status in JIRA with whatever the previous assignee was set to.

The use case is a requirement to have a single Aha! Initiative create/map to Epics that are in different JIRA Projects. Current support is that an Aha! Initiative can only be linked to a single JIRA Epic. Simple example: Fredwin Cycling has an Epi...

Sometimes we need to investigate synchronisation errors between Aha! and Jira. We can find these errors long after an initial error might have happened. We might need to go back to the original error which may have happened months ago. The limitat...

Who would benefit? Anyone using Jira integrations What impact would it make? "Parent Link" and "Epic Link" fields have been replaced by a new "Parent" field in Jira. By recognizing this new field, integrations will not break and can use the new fu...

When adjusting settings that are referenced in an integration, there is no warning that integrations will be impacted and users are not guided to update their integration settings. There are two main settings that result in notable issues in the i...

Some of our fields in Aha are solely dictated by the field in Jira, for example Status. Statuses in Jira have validations, which cannot be recreated in Aha. If we map Status bi-directionally, we run into errors because Aha is trying to overwrite...