Work with Confluence for PRD Documents

Currently we use Confluence PRD documents:

It would be great if we could find some way to combine this with Aha. Otherwise, we spend time duplicating information from inside Aha to the PRD documents. 

  • Guest
  • May 20 2015
  • Already exists
Release time frame
  • Attach files
  • Admin
    Danny Archer commented
    May 26, 2015 23:26

    Hi there,

    Could you elaborate a bit more on what you are looking for? You can already create similar documents in Aha! through Product -> Notes.

    If the team wants to continue using confluence pages, you can always link to the pages within Aha! - it is not clear what you want to get out of us "working with" the documents in confluence.

  • Florian Leray commented
    June 25, 2015 16:08

    Hi Danny,

    Product -> Notes : do you mean you would document all product requirements through this system? On my side, I don't see where to link each note with a feature or a requirement so that it's well structured, at least.

    Coming back to Confluence, I wasn't able to find where to link a Confluence webpage to a feature or a requirement within Aha. One can attach googledrive files and so on, but not a simple web URL, right?

    To "solve" the issue, we created a custom "Confluence Link" in Aha! features in order to store this link, but we have to copy-paste that link manually on our browser in order to reach the Confluence page.

  • Admin
    Suzanne Vaughan commented
    July 11, 2015 13:22

    Hi Florian,

    You asked a couple of question so I want to take them one at a time:

    1) To link to a feature or requirement (or other object) in Aha!, you can use # and it will allow you to search for those objects. Please see using @mentions and #mentions.

    2) If you want to link to a Confluence page directly you can paste the URL into the description or do what I did above and add a hyperlink using the editing tool. This way you can skip the step of manually copying/pasting. Just click on the link. Hope that makes more sense. 

  • Admin
    Ron Yang commented
    November 04, 2015 21:08

    Danny and Suzanne's suggestions are the best way to either create requirement documents in Aha! or leverage requirement documents which already exist in Confluence.

  • Guest commented
    January 14, 2016 21:56

    Hi all, I wanted to elaborate a little more on this. Here is what I currently do throughout my design process with Developers around a PRD.

    1. Initiative is created in Aha!, this creates a Epic in JIRA. 
    2. In Confluence I create a PRD for this Epic/Initiative. I put a link to this Confluence page in Aha! Initiative. 
      1. The PRD contains details of individual requirements and stories. Once we discuss with developers and agree on PRD, developers will create JIRA Stories from the PRD. 
      2. These Stories in JIRA are then associated with the Epic. 
      3. The Aha! integration then creates Features in Aha! and links them to the Initiative since they are all connected to the JIRA Epic. 

    This is my current process when designing a PRD. Confluence has a lot of collaboration features that really make the design process of a PRD pretty smooth when working with a distribute team. Things like in-line comments with Resolution, integrations into JIRA, configurable layouts, links to other wiki material for reference, mockup tools, etc. really make it the tool of choose to quickly design PRDs and getting collaboration around them. 

    Aha Notes are useful but not quite as powerful as Confluence Wiki Pages. I would be interested in seeing if we can bring content between both system together in some way. No immediate ideas off the top of my head but I would like to start a conversation around it.  

  • Sébastien Miglio commented
    March 07, 2016 15:44

    I do agree that after trying Aha! document editor I went back to Confluence for all requirements, themes and other product related materials. Currently we are heavily relying on Confluence for documents and I don't see how I could switch completely to Aha!. As such we did implement custom field in Aha! to link to Confluence page, not ideal but it works.

    Same happens the other way around, I would like to expose the Roadmap in Confluence by inserting Aha! widget but I have not found yet how to do this.

  • Christian O. Petersen commented
    June 20, 2016 17:37

    Hi Guys

    I don't agree that this already exist. It is clear that if Aha! was able to publish to confluence and then do 2-way updates like it does with Jira that would be an amazing addition. Aha! is a great tool for product managers, but we are not going to get thousands of our developers to use it every day like they do Jira and Confluence. By not having as good integration with Confluence as you do with Jira, you risk a lot more push back as Product people try to get Aha! adopted across their organizations.

    - Christian O. Petersen, Comcast Silicon Valley Innovation Center

  • ravi singhvi commented
    July 18, 2016 22:41

    Agree with others on this board - Integration with Confluence does not exist.  Creating a hyperlink is not integration.

  • Guest commented
    November 17, 2016 14:32

    Agreed - I don't believe this exists today and we need something more comprehensive.

  • Tyson Kretschmer commented
    June 01, 2017 04:01

    I agree that it does not exist and I believe I came up with the Confluence integration solution everyone is looking for in this Idea:

  • Guest commented
    September 20, 2017 12:46

    Yes I have to agree sadly. AHA doesn't really cater for an approach that predicates everything from a PRD it feels like the notes page is just an afterthought. There is a help section on using a PRD but it doesn't really feel like AHA buys into this and prefers to jump straight into initiatives and user stories and then use a report to create the PRD afterwards. Bit like summarizing all your tactics at the end of the year and then saying it was your strategy. I really like AHA but I have to manage the PRD separately in word documents, create individual traceablity matrix for each epic and then import these via a CSF into AHA to create the user stories. So not ideal but  who of us doesn't like a challenge.  I use word rather than confluence now because of data portability. Much though I like it its quite a rigid application and very time consuming to export a document externally as it invariably needs a half a day to reformat it.