Need to "Link with existing issue in JIRA" at requirement level
We have JIRA and Aha today and the tools are integrated as follows:
Aha feature - JIRA Epic
Aha requirement - JIRA story
NA - JIRA sub-task
For some reasons, I had to delete the integration with JIRA for a specific product line...
Would like to be able to view the sprint a feature is currently assigned to in JIRA. It looks like we have most of the other fields available for mapping but that one isn't available. I get a ton of questions about when a feature is scheduled to b...
Integrations 2.0: Support "Link to existing" functionality from 1.0
In 1.0 you had the option with JIRA to link to existing records.
This would let you connect an existing record in Aha! with an existing record in JIRA.
This support should exist for 2.0 integrations.
Danny Archer
over 6 years ago
in Integrations
8
Shipped
Ability to "lock" a custom field, so no user can edit it
Some of our fields in Aha are solely dictated by the field in Jira, for example Status.
Statuses in Jira have validations, which cannot be recreated in Aha. If we map Status bi-directionally, we run into errors because Aha is trying to overwrit...
We use confluence as a platform for detailing product development plans. It would be great if one was able to embed notebooks from Aha! within confluence pages or indeed easily allow Aha! data to be inserted into confluence.
A set of macros, a...
If you assign a JIRA issue to be unassigned, the assignee is not reflected in Aha! correctly which causes the next Aha! update to overwrite the unassigned status in JIRA with whatever the previous assignee was set to.
Allow for a unique identifier to match on in the SF integration
We have multiple accounts with the same name in Salesforce, like Boeing (accounts for each location). In order to select the correct org from a drop down, e.g. to assign an idea to an org, we have appended each account with the client id (so it ap...
Sara Olson
almost 2 years ago
in Salesforce
0
Shipped
Support for an Aha! Initiative to create/map to Epics across multiple JIRA Projects
The use case is a requirement to have a single Aha! Initiative create/map to Epics that are in different JIRA Projects. Current support is that an Aha! Initiative can only be linked to a single JIRA Epic. Simple example: Fredwin Cycling has an Epi...
Epics on top of feature were introduced with VSO a few weeks ago.
The VSO Connector should be able to reflect that somehow. Either by also working with epics in aha that encapsulate features or better the easy MVP way with a global setting for the...