Allow a Feature (epic) in Aha! to have Requirements (stories) that live in a different Jira project
The use case is that we create features in Aha! and sync them to Jira as epics. The development team will then break the epics down further into stories in the appropriate Jira projects for the teams that need to work on them. In Jira, these stori...
Jira tickets support embedded images using the following format. !ImageURL! for example: !https://imageurl.png|width=50%,height=auto! Jira Image Formatting Notation We make very heavy use of this feature to pull our designs into the jira tickets s...
We have different workflows in JIRA for our Epics/Charters than we have for estimates or actual work tickets. It would be nice if when setting up the integration we could individually map both the feature and the requirements status messages indiv...
It would be useful to have the account value linked to an idea that's generated from the account page, similar to how it's currently done for opportunities.
Aha! integration with should create a hyperlink record in TFS to link back to the Aha! item
Aha! integration with TFS should create a hyperlink in the TFS item when the Send to Team Foundation Server action is selected and a new TFS item is created. Additionally, an action that sends a link record to TFS would be helpful if the link is l...
Currently you are able to send features to Trello from Aha and their status will be updated as they are moved in Trello. However comments and attachments that are added to Trello cards/features do not move to Aha. Enabling this feature would allow...
Automation rule to update already integrated records
Currently, automation rules provide the ability to send an Aha! record through an integration based on the record being updated in a specific way. We would like for the ability to push updates to already integrated records in the same way. This is...
When adjusting settings that are referenced in an integration, there is no warning that integrations will be impacted and users are not guided to update their integration settings. There are two main settings that result in notable issues in the i...
Madeleine Black
over 2 years ago
in Jira
0
Shipped
JIRA Import multiple issue types as requirements mapped to parent feature
As a PO, I’d like to import multiple issue types (i.e. bug, story) as requirements that map to their parent features so that existing Jira Projects can be imported into Aha! Products in a single import
Danny Archer
almost 10 years ago
in Jira
4
Shipped