RELATED IDEAS
Integrate Aha! and Confluence to link Confluence Pages in AHA! and transfer them with JIRA
Atlassian currently offers the ability to Integrate Confluence & Jira using Application Links which gives teams multiple features.
https://confluence.atlassian.com/doc/use-jira-applications-and-confluence-together-427623543.html
One of the features we utilize heavily is the ability to Move between Jira & Confluence.
Whenever you add a link to JIRA issues in Confluence, or link to a Confluence page from your JIRA application, the JIRA Links button appears at the top of the Confluence page. This makes it really easy to jump from Confluence to JIRA and vice versa, speeding up your workflow.
The great thing about the Confluence Links in Jira is that they are dynamic and change if the page is renamed or moved in Confluence.
I believe that it would be a great benefit to integrate Aha! and Confluence to do the same thing. Once integrated the Confluence links can be added to Aha! feature and then passed to Jira through Feature field mapping. This would save time as currently I create a Feature in Aha! then send it to Jira and have to remember to go and add the Confluence Link in Jira.
Here is how it would work once Aha! & Confluence are integrated:
- Create a Confluence page using the Product Requirements Blueprint.
- Create a Feature in Aha! and link it to the Confluence page (same way as done in Jira by searching for the Confluence page)
- Send Feature to Jira using 'Send to JIRA'
- Confluence page link is automatically transferred JIRA Issue
This tight integration between Aha!, JIRA & Confluence means that you can easily access the Confluence pages within Aha! and they can be transferred to JIRA and vice versa.
-
ADMIN RESPONSEOct 9, 2019
Thanks for the idea!
We wanted to let you know that we now have a new integration with Confluence.
Share a live view of an Aha! roadmap, report, or presentation in Confluence — so you can further promote your brilliant plans across the organization.
Learn more: https://blog.aha.io/aha-confluence-integration/
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- +130
1
MERGED
Integration - Confluence > Aha!
Our POs need to update user story summaries separately in Aha! and Confluence. If we had the ability to embed Confluence page info in Aha! and update the info from Aha! (push updates to Confluence) it would streamline information management. We us...
0
Future consideration
43
MERGED
integration with Confluence to sync Aha feature description with Confluence pages
We gather rather complex information on new increments in Aha feature descriptions, when those get developed information need to be transferred into our Company Wiki to provide all Company Members and some Partners access to it. Our Confluence Wik...
0
Future consideration
Integrating Confluence with Aha! will be a huge help to our Product Managers. Easy access to PRS and TDS documents without having to make multiple clicks.
Is this on your roadmap?
What I am looking for is a way to embed the confluence page into Aha. Like an iframe or similar. We have many 'work spaces' in confluence that would be useful to see in the associated feature or ideas from a Product Manager perspective.
Our Development Team relies on JIRA and Uses Confluence Heavily for Documentation Management. Having Templates from Aha! Feed directly to Confluence or having them stored with the synched Link in JIRA would be a significant upgrade
Notes and Confluence serve the same purpose in alot of ways. In order for a Product team to rely on the sole use of Aha, you need to be able to sync the Aha! notes-> jira->confluence. In a multi system environment it will allow for the free flowing of information and Official documentation. Between the systems as needed
Step 3 : sending feature to Jira - as a story?? The problem i'm having is the story is only 1 story of many to get a feature done -need to break the story into multiple stories. The original story may get marked as "Done" but the other stories aren't Done, so AHA is incorreclty showing the feature as DONE, but it's not. Can you suggest a process please for updating AHA once multiple stories are done for the feature.