Jira

Showing 260

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 over 9 years ago in Jira 0 Already exists

8 VOTE

Map Aha! products to Jira components

Allow the mapping of Products in Aha! to Component/s in Jira. In order to automatically assign Aha! items pushed over to Jira to the right component, I've had to create a custom field in aha! with a pick-list of the component names from Jira. I c...

Max Cascone over 7 years ago in Jira 3 Already exists

1 VOTE

Defect: Jira Integration record mapping doesn't use custom terminology

Who would benefit? Anyone with custom names for "Epic" or "Feature" who is setting up a Jira integration. What impact would it make? Prevent failure of the integration (which took us several hours to figure out). This was particularly egregious fo...

Guest 12 months ago in Jira 0 Future consideration

5 VOTE

Set Rank order from Jira to Aha!

When configuring a new Product in Aha to integrate with Jira: The backlogs are already in priority order in Jira. However, when syncing over to Aha!, the priority order does not carry over upon the first sync. I understand how to use the rank fiel...

Guest about 5 years ago in Jira 1 Future consideration

1 VOTE

Excel Transfer to Jira

Who would benefit? Developers What impact would it make? Better requirements How should it work? Excel transfer to Jira because Jira does not support merged cells

Guest about 1 year ago in Jira 1 Unlikely to implement

5 VOTE

Integration history

Would like to track when a feature was sent to JIRA and by who? Can you please let me know how I can accomplish this? JIRA_KEY (I am able to pull) JIRA_KEY_CREATE_DATE (Not known) JIRA_KEY_CREATED_BY Thank you //Need this for SOC compliance//

Sasi Ravichandar about 5 years ago in Jira 0 Future consideration

5 VOTE

We need the Initiative ID available in JIRA integrations so they can be reference-able in other tool dashboards.

We use the Aha API to populate views in Tableau. The Initiative [API] ID is a crucial portion of making sure what we sync to JIRA from Aha and what we are looking at in Tableau which provides a combined view of both tools, is one and the same. I a...

Wen-Wen Lin over 5 years ago in Jira 1 Future consideration

4 VOTE

Ability to apply a Jira Integration Template to an EXISTING Jira Integration but only have it update the URL and Jira Login/Password settings

We had a very large number of Jira Integrations created before we had central administration of our Aha application. I need to apply a Jira template to these integrations so that the URL and password can be managed from a central person, but if I ...

Leanne Miller over 4 years ago in Jira 0 Future consideration

7 VOTE

Support all types of JIRA text field formatting

The current JIRA integration doesn't support renderers other than the Wiki Style Renderer very well. Please add support for the other renderer types.

Guest over 7 years ago in Jira 0 Unlikely to implement

1 VOTE

Jira Integrations: Map Aha Releases to a custom Jira Version Field

Who would benefit? Any Aha customer with jira integration that uses a separate jira field that has version data as values to enter. In my jira project I use a different field (other than fix version) to track what release our features will release...

Kyle Shannon about 1 year ago in Jira 0 Future consideration

Share your product feedback

Please enter your email address

FILTER BY CATEGORY