We are testing an update to Confluence 5.4 and very much look forward to the better JIRA integration. Hilighting text on a confluence page and using it to open a JIRA issue is quite handy. Having this process automatically add a jira-issue macro to the confluence page as part of this process is not.
How do you prevent this process from adding a jira issue macro to the confluence page? Revoking page edit permission to users is not an acceptable solution.
After discussing the issue with support, the intended behavior of this feature is to interface with the Jira Issue macro and to add the issue macro to the page. Opening a ticket is a function of the macro.
After discussion and to prevent our users from adding issue links accidentally to our documentation pages we disabled the pop-up portion of this feature. When I disabled the "Confluence and Jira Content Connector" Plugin, the popup stopped showing up.
It's a nice feature, but is not needed in our implementation at this time.
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