Jira

Showing 45

Automated or Scheduled Import from Jira

Enable an automatic or scheduled import of tickets from Jira. My dev team creates tickets on a range of projects over the course of the week. I'd like the ability to have these loaded into Aha before my weekly sprint planning meeting so I can ass...

James Conklin over 7 years ago in Jira 0 Already exists

4 VOTE

Allow users to name "Send To JIRA" when multiple JIRA projects are integrated

Allow users to name "Send To JIRA" when multiple JIRA projects are integrated Currently, I have three JIRA projects integrated to a single AHA product: LCI TEAM METHD UXH Currently, these three projects show up as Send to JIRA Send to JIRA Sen...

Guest over 7 years ago in Jira 5 Already exists

1 VOTE

Update JIRA with updated Aha Requirement definitions

When we update a requirement in Aha with a new or updated requirement definition, and there is already an existing JIRA link, the updated copy doesn't transfer over to the JIRA User Story, even when we select "Update JIRA" from the Actions menu.

Guest over 7 years ago in Jira 1 Already exists

4 VOTE

Tickets linked to JIRA should link back to Aha.

We are currently pushing Aha! tickets into JIRA. It would be helpful to have a link in Aha-created JIRA tickets that linked back to Aha (the same way Aha! has a ticket number and link to the JIRA ticket).

Guest almost 8 years ago in Jira 0 Already exists

2 VOTE

Need an option to sync Jira fixVersion "Name" instead of "ID"

Aha! Feature may contain Requirements from different Jira Projects. Right now, the fixVersion is synced with "fixVersion ID", which will not be synced successfully when the Feature (Epic in Jira) and Requirement (Story in Jira) belong to different...

Guest over 8 years ago in Jira 0 Already exists

1 VOTE

Provide the ability to map multiple ticket types to requirements

We are hooking Features into Epics, and discussing with development and the rest of the product team, the individual enhancements, new features, and tasks that are required to be performed for the "Epic" to be completed. Aha/Jira integration only ...

Guest over 8 years ago in Jira 3 Already exists

18 VOTE

Allow the JIRA integration to support mapping to more than one JIRA issue type and in Aha provide the ability to select the JIRA issue type to sync with

We use Aha for both Feature Requests and Defects and need to be able to designate if the JIRA issue type is an Epic, Story or Bug when linking to JIRA.

Kevin Konishi almost 9 years ago in Jira 11 Already exists

3 VOTE

Link Features to Multiple JIRA Projects

This would be useful in sending features to more than a single JIRA project. Our development teams are organized around services and platforms and often end user product releases rely on multiple JIRA projects and teams. It would be ideal to link ...

Ryan Schultz almost 9 years ago in Jira 0 Already exists

10 VOTE

Allow users to refresh all Aha! features from a linked JIRA integration.

Currently, only the changes made to a JIRA issue are sent over to Aha! through the webhooks. We should have a way to force Aha! to synchronize all descriptions and fields from JIRA for an entire release.

Alex Bartlow about 9 years ago in Jira 0 Already exists

1 VOTE

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

Andrew Tipton about 9 years ago in Jira 2 Already exists

Share your product feedback

Please enter your email address

FILTER BY CATEGORY