Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Jira

Showing 262

Complete Auto Import Functionality -- not just children of existing linked records

This is regarding the JIRA integration feature: Automatically Import New Records: Records will be imported automatically to Aha! from Jira. This applies to records which are created as children of previously linked initiatives, releases, master...
Guest over 5 years ago in Jira 5 Future consideration

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 versio...
Danny Archer about 9 years ago in Jira 15 Future consideration

Support updating JIRA Integration Links by csv upload

While I recognise that moving JIRA issues between projects breaks the AHA integration links, the workarounds proposed here are not helpful. Option 1 ("Relink each record manually") is the only viable workaround, with options 2 and 3 being too haza...
Garret Duffy over 1 year ago in Jira 0 Future consideration

Provide alternative way to match users when email address is not exposed in Jira

Some time ago, Atlassian made changes that requires users to share their email addresses on an individual user profile setting. When that option is not checked, Aha! is not able to view their email address and if assigned user is mapped, is not ab...
Madeleine Black about 2 years ago in Jira 1 Future consideration

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 over 5 years ago in Jira 4 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 over 7 years ago in Jira 5 Future consideration

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

In integrations 1.0 if I mapped Features = Story Requirement = Task Aha! 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. ...
Danny Archer almost 7 years ago in Dependencies / Jira 3 Future consideration

Epic progress doesn't update when it has children in different projects

Who would benefit? Customer using Jira epics to manage work in multiple projects What impact would it make? They would be able to see their progress in Aha! correctly How should it work? If you have an epic in Project A, and it has multiple childr...
Kyle d'Oliveira 9 months ago in Jira 0 Future consideration

Jira integrations : Add the capability to use filters instead of boards to set up integrations

What is the challenge? the boards only have tickets currently worked on , we want to load all tickets , so we can plan , this is because the team sometimes their create their own What is the impact? if you need to split a jira project with multipl...
Guest 2 months ago in Jira 0 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 about 9 years ago in Jira 12 Planning to implement