Best practice: Using JIRA and CONFLUENCE together

[Thomas Burkhart]

We want to use JIRA and Confluence together in our new project.

Now the question arises what to do where. Do I better put requirements into JIRA with all details? This may make it harder to discuss and refine them in the team. Or do I put detailed descriptions in CONFLUENCE and only link from JIRA to the confluence pages?

What are youre experiences?

[Remon van G]

We find confluence is great for architecture, project dashboard and manuals (and discussions also), and as above use Jira for all individual elements like requirements, tasks items etc. So more the Meta information that goes to Confluence.

[Bob Swift OSS (Bob Swift Atlassian Apps)]

Yes, that is generally what we do. JIRA is used to track the requirement, design, etc... and then if there any significant supporting detail information and discussion, it is linked to a Confluence page. In many cases the Confluence page is a design template etc...

[John Burns]

We put all requirements and details in confluence, then create tickets for each individual requirement. We use the Insert -> Jira Issue macro to link a requirement on confluence to its related Jira issue. This way, when we need to make a change to a requirement (enhancement), we can add another Jira Issue macro, and all work history will be shown on the Confluence page, even though only the latest version of the requirement is spelled out.