We have JIRA and Confluence (Cloud versions... formerly OnDemand). Most of our organization uses Confluence, but only the Developers use JIRA (Agile).
However, the Confluence users do need read-only access to JIRA issues info, mostly to see reporting on general state of the issues the Developers are working on.
We wanted to include the JIRA Issues Macro on a Confluence page that the rest of the organization can look at to see the issues we're currently working on in a Sprint (and their status), or the issues that are still in the Backlog (and their rank).
However, non-JIRA users get permission denied on the Macro. I've looked online, and for non-cloud versions, you can define the authentication type so that you can define the credentials that the macro runs under. How do we do this with Confluence Cloud? I have no problems using a JIRA license for read-only abilities to issues, but I need the ability to define the context for the JIRA Issues Macro.
To me, this is basic functionality that I believe most companies need. What is the solution?
Most of us don’t need much convincing that stakeholder management is important. It just makes sense that keeping everyone in-the-know on projects and assigning clearly defined roles is key to having ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs