ADD A NEW IDEA

Jira

Showing 245

JIRA integration - Send to JIRA - labelling

Hi Guys We have mutiple JIRA to single Aha! product, so when sending we see the image attached. You cannot distinguish which JIRA in this list - please extend to: Send to JIRA: VIS - where VIS is the name of the JIRA project. Seems a simple qu...
Andrew Tipton over 8 years ago in Jira 2 Already exists

Allow tracking simultaneous tracking of both Feature-Level and By-Requirement estimates

The current AHA/JIRA estimate integration allows feature level OR requirement level estimates, however as we don't use JIRA for time tracking we want to use JIRAs 'Original Estimate' field with AHA's per-requirement estimates. My suggestion would...
Guest over 8 years ago in Jira 0 Unlikely to implement

Pull JIRA Original Estimate not Remaining Estimate

We use sub-tasks or even regular tickets in JIRA to do our estimates so they can be planned into sprints. When these estimate tickets are closed on the JIRA side it seems that the estimates they are for are zeroed out on the Aha side. The only thi...
Guest over 8 years ago in Jira 0 Already exists

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 over 8 years ago in Jira 15 Future consideration

Assignee does not get sent to Jira if using Default Assignee functionality

If you use the "default assignee" functionality, then that assignee will not get sent to Jira, even if that user exists in Jira. This could be considered a bug.
Avigail Ehrenhaus over 8 years ago in Jira 0 Already exists

Support mapping JIRA Tempo Account field

When using the JIRA Tempo plugin to track work time, it is useful to link issues to Accounts - for this the plugin exposes a custom field named Account. This field, formerly called Billing Key, is used among others in reporting, to decide which cu...
Guest over 8 years ago in Jira 8 Unlikely to implement

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 over 8 years ago in Jira 10 Likely to implement

Allow To-Do's to be mapped to JIRA Issue Types

We would like to be able to make better use of Aha To-Do's so that they carry over to our JIRA Agile installation. Currently we have Initiatives mapped to Epics, Features Mapped to Stories and Requirements Mapped to a custom JIRA type of Requireme...
Guest almost 9 years ago in Jira 5 Unlikely to implement

Map Aha! final score to JIRA priority

We manage the product through Aha! and the priority of features with Aha! Score. Product management can be easier and more efficient with an option to inform developers about priorities directly from Aha! to JIRA (We use JIRA Standard and Agile in...
Guest almost 9 years ago in Jira 9 Future consideration

Convert story to epic in Jira when promoting requirement to feature

In Aha! I have a feature with a set of requirements, all of which has been pushed to Jira as an epic with a set of stories. I want to convert one of the requirements to a new feature in Aha! and have the corresponding story in Jira changed to an e...
Guest almost 9 years ago in Jira 2 Future consideration