Howto list Jira-issues in confluence

[Hugo]

Hello,

we have an application link between our jira and confluence instance. Confluence is licensed for 2000 users and Jira for 25.

Both servers have an Active Directory as a User Directory.

Currently we cannot list/create Jira-Issues within confluence.

What is the exact procedure for assigning rights to AD-groups so issues can be listed/created in Space X from/for the Jira-Project Y

Space X

Jira-Project Y

Thank you,

Michael

[Jonathan Smith]

Hi @Hugo,

  Below is from our Confluence Server 6.6.1 environment.

• Confluence server 2000 users
• JIRA server 500 users

Confirm you are "connected" to JIRA in your Confluence application links.

• Confirm you now have the JIRA macro.

If connected, you should be able to go to a Confluence page, edit the page, and add the JIRA macro.

Edit the macro and insert your favorite JIRA filter JQL:

When users first see a JIRA linked page, they may get a message at the top of the page that says "authorization required", they will need to click accept if they are one of your JIRA users.

• The authorization message is a 1 time notification

I don't believe we did anything different when it comes to active directory. We have various groups nested under jira-core-users and confluence-users.

Confirm the user has access to the Confluence space and the JIRA project.

---------------------------

Troubleshooting question

• Is the application link "connected"?
• Can anyone see the JIRA content on the Confluence page?
• When you highlight Confluence text, do you have the JIRA icon beside the comment icon? If not, definitely sounds like an application link problem.

Regards,

Jonathan

[Hugo]

Hello Jonathan,

thx for the answer.

The links on both sides are "connected". The setup is the following:

Our Confluence-Server "confluence-original.xyz.com" is behind a proxy "confluence-proxy.xyz.com" - SSL of course activated.

The Jira-side Link:

Application URL: https://confluence-proxy.xyz.com/wiki

Outgoing/Incoming: OAuth(impersonation)

The Confluence-side Link:

Application URL: https://jira.xyz.com

No proxy

Outgoing/Incoming: OAuth (impersonation)

Within Confluence the Jira-Macro is visible.

When we want to create a new issue through the macro it says "You don't have permission to create issues on this jira-server" - or something like this, I'm translating.

Adressing issues through key = "xyz-10" gives the info "No search result could be found, although the issue definitely exists AND the user logged in within confluence can see that issue in Jira.

Any ideas?

thx.

[Jonathan Smith]

@Hugo My current setup is:

Try connections = OAuth

• Whenever you change these settings, make sure you are doing this in DEV first. 

The only other thing I remember about this setup was having to add a certificate to the trust store. 

If none of these suggestions work, I would request someone with higher system admin knowledge to respond or the Atlassian Team to look into.