My ideas: Jira

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...

What is the challenge? If you introduce Version<>Release mapping to an existing integration or you link a record to an existing Jira record, subsequent updates are creating a new Aha! release (linked to the Jira issues's Fixed Version) but t...

If we already have issues in JIRA that are duplicates of features in Aha! we want to be able to manually create a link between them.

Why is it useful? Our Product team uses tags in Aha and labels in jira to help in planning which team works on which requirement / user story, to make sure that one team working in the release is not over-burdened. Sometimes one team works on an ...

In 1.0 you could map Features to Stories but also set the JIRA integration to support importing unmapped types. This meant that bugs, tasks, etc created in JIRA could be imported as Features in Aha! This is important, without this we have no way t...

We have different workflows in JIRA for our Epics/Charters than we have for estimates or actual work tickets. It would be nice if when setting up the integration we could individually map both the feature and the requirements status messages indiv...

Jira tickets support embedded images using the following format. !ImageURL! for example: !https://imageurl.png|width=50%,height=auto! Jira Image Formatting Notation We make very heavy use of this feature to pull our designs into the jira tickets s...

The use case is that we create features in Aha! and sync them to Jira as epics. The development team will then break the epics down further into stories in the appropriate Jira projects for the teams that need to work on them. In Jira, these stori...

When users set up an integration and select "auto import records", they are not immediately aware that some records will not just automatically import into Aha! (i.e. those that don't have a parent record that is sync'd). These users are not able ...

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...