Why would I use Project Links between Jira & Confluence and Bitbucket & Confluence?

Hans Polder_7ci2ta

I have an environment with 3 products:

• Jira 9.12 DC
• Bitbucket 8.19 DC
• Confluence 8.5 DC

All three environments are linked with Application Links. However, I'm now struggling to find any documentation on using Project Links between these products.

The only reasonably clear documentation is only explaining specifically what specific benefits I would gain from creating an Application Link between Bitbucket towards Jira (from Bitbucket's perspective).

However, I'm struggling to find anything about the other possible integrations:

1. Jira > Bitbucket
2. Bitbucket > Confluence
3. Confluence > Bitbucket
4. Jira > Confluence
5. Confluence > Jira

 

So: What functionality is gained if I go through the trouble of adding project links on top of Application Links?

 

Seon Shakespeare

Hi Hans,

Great question!

Many core integration features between Jira, Bitbucket, and Confluence work with just Application Links. You can already view linked development info in Jira, embed filtered data in Confluence, and more.

Here's my take on Project Links and what extra benefits they bring:

• Easier setup: They can pre-configure some integrations. For example, if you want to display Jira issues from a specific project on a Confluence page, a Project Link might automatically pre-select that project in the Jira Issue Macro, saving you from writing a JQL query.
• Better navigation: They can provide contextual links between projects, repos, and spaces.
• Deeper integrations (sometimes): Some apps or features might need them for more advanced functionality. For instance, a release management app might use Project Links to automatically connect Jira issues with the right Bitbucket repositories.

Basically, Project Links can enhance the integration experience, but if Application Links are working for you, you might not need them.

Hope this helps!