Skip to Main Content
ADD A NEW IDEA

Jira

Showing 169
164 VOTE

Dedicated Integration User

It would be great to have a dedicated integration user instead of having to use a user license for this purpose. I would love to keep my user and the updates from integrations (Jira, TFS,...etc) separate so that it is clear who made the update in ...
Guest over 7 years ago in Integrations / Jira 16 Future consideration
150 VOTE

Sync record's workspace, goal, initiative, epic, and release (name and link) to Jira

The use case is so that those working primarily in JIRA can understand “why” they are being asked to deliver “what” has been requested. In the screenshot attached, it shows a section of the JIRA issue interface. It then shows a tab created specifi...
Project Parker over 6 years ago in Jira 8 Future consideration
124 VOTE

Integrate ideas with Jira

What is the challenge? Companies that use both Jira and Aha! ideas must go through extra steps to send information between the two systems. For example, if a small fix comes in as an Aha! idea, it must first be promoted to a feature or requirement...
Kelly Sebes 3 months ago in Ideas / Jira 2 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 ver...
Danny Archer almost 9 years ago in Jira 15 Future consideration

Move Aha! Requirements when linked JIRA Stories are Moved to a different Epic/Feature

The specific use case that this commonly occurs for is the following mapping: Feature = Epic and Requirement = Story; however, the same would apply to other mappings parent child mappings such as Story/Sub-task as well. Current behavior: The int...
Matt Case about 8 years ago in Jira 13 Future consideration

Jira Integration of custom calculated field

We have a Jira project that supports multiple engineering teams. Each team has their own release schedule. We need a way populate fixversions in jira with team specific values. The creation of a custom field that combines "product prefix-release n...
Russell Roach almost 4 years ago in Jira 3 Future consideration

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

Add 2-way integration mapping for release start and end dates

Release start date can currently only be mapped 1-way from Aha! to Jira (or any development system.) This is because that date used to be calculated based on features and phases in the release. Now that this date is set manually, it should be poss...
Austin Merritt over 4 years ago in Azure DevOps Services and Server  / Integrations / Jira / Rally 2 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 about 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 mappedFeatures = StoryRequirement = TaskAha! 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.In 2...
Danny Archer over 6 years ago in Jira 3 Future consideration