Skip to Main Content
ADD A NEW IDEA

My votes: Jira

Showing 247 of 8599

Aha Integration Status Criteria

In Integration, I am not able to choose which statuses I send and which status changes I do not. Example, captured, i do not want to send, but Aha Integration allows me to send to down stream systems with a blank mapping. Please enhance integratio...
Sasi Ravichandar almost 5 years ago in Jira 0 Already exists

Add Product Prefix field as a choice in the JIRA integration

We integrate Aha! with multiple JIRA projects and often use the product prefix as the Component to identify the source of the ticket. Today we use a constant and add that manually. Adding it from the prefix would save us a lot of time!
Guest about 5 years ago in Jira 0 Future consideration

Allow for "approve incoming changes" in Jira integration

There is currently an option to approve outgoing changes or incoming records, but not incoming changes. The current options are: - Allow any Jira user to directly impact sensitive Aha roadmap information by changing Jira tickets (we map Epics to...
Guest about 5 years ago in Jira 0 Future consideration

Merge Custom Fields into One Field when they are carried over from Idea to Feature

At idea stage you capture information about the idea in multiple fields, when you promote this to a feature if this information was merged into one 'Body' field, then I would save time not having to copy and paste those fields into one field. ...
Guest over 5 years ago in Jira 0 Unlikely to implement

Integration Updates > Send Changes > Add Release filter & Status filter

On the Aha! Integration Updates screen for an Aha! to/from Jira Integration, I would like to see which releases and the status of what each of the items are for integration. Being offered these filters would allow me to select that before importin...
Guest over 5 years ago in Jira 1 Unlikely to implement

Attachments linked to Note custom fields should be supported in Integrations 2.0

The note custom field allows for documents to be attached. However, when "attachments" are synchronized between Aha! and the development system, only attachments linked to the Description field are sent over. It would be ideal if the documents att...
Guest almost 6 years ago in Jira 0 Future consideration

Import Feature Requirements from Jira 2.0

It would be helpful if Requirements were built out so that they can be imported from jira 2.0 AND moved from feature to feature as easily and features are moved betweeen master features.
Kaylee gervasi about 6 years ago in Jira 0 Already exists

Manual selection of items selected for import from Jira

As a user of Aha! and Jira I want to be able to select the items that get imported from Jira so that I can more easily coordinate and synchronise the data held in the two products. There are two main tools that allow data to be brought into Aha! f...
Guest about 6 years ago in Jira 0 Unlikely to implement

Jira 2.0: modify integrations based on templates

In 1.0, when using a template, you could choose what fields/behaviors to inherit from the template, and which to customize for that particular integration. This was useful for custom fields (now using a constant in 2.0) which will change from prod...
Max Cascone about 6 years ago in Jira 6 Already exists

Allow integration of Custom Fields to any Jira Field of a supported field type

We have a process where we track issues reported by Release. Our issues come via Cases in Salesforce, which are then pushed as an Feature in Aha which captures the Affected Version in a custom field. We would like to push this custom field valu...
Guest over 6 years ago in Jira 0 Already exists