Structure.Pages is an extension for Structure plugin that lets you create, manage and organise Confluence pages alongside JIRA issues right inside Structure.
Once you connect your JIRA and Confluence with Application Links and configure Structure.Pages you'll be able work with pages from your Confluence in a similar way you work with issues:
Structure.Pages provides integration between JIRA and Confluence so its installation requires a bit more work than installation of a plugin that only works with one system. But fear not - follow the steps described below and you'll have it running in no time. And if something goes wrong, please don't hesitate to contact us at firstname.lastname@example.org.
Here's what you'll need to do:
To make your JIRA and Confluence work together and exchange data you need to set up Application Links. You can find all the details on how they work and how to set them up in Atlassian documentation.
Atlassian recommends using OAuth protocol because of the greater security provided by that protocol and Structure.Pages supports this and other available protocols.
To allow Structure communicate with Confluence you need to install a small add-on for Confluence. This add-on does not require any additional configuration and once installed it will take care of the integration with Structure on the Confluence side. You will also need to enable Remote API (XML-RPC & SOAP) in Confluence. Use menu Administration | Further Configuration. Structure.Pages needs XML-RPC to access methods not available through the REST API.
JIRA add-on for Structure.Pages requires a bit more work:
Install Pages add-on for JIRA the same way you installed the add-on for confluence.
Select the System Authentication method. The drop-down shows all authentication types you have configured in the Application Links.
It's recommended to choose the one that would allow Structure.Pages see the most of the Confluence. All users who will work with Confluence via Structure.Pages will see a sub-set of pages that System Authentication permits to see, so if System Authentication permissions are more restrictive than the user permissions, the user won't be able to see some pages that should actually be visible.
OAuth method is preferred here and it's recommended to use admin user for this authentication.
The simplest way to get started is to add some of the existing pages to your structure:
Once the page is in a structure, you can see the page contents and edit it.
To do that simply click this page name in your structure and it will be shown in the panel on the right. You can work with it as if it was a usual Confluence page opened in a browser. You can click Edit to start editing the page contents or use any other available controls.
If you are not logged into the Confluence in the same browser session, you will be prompted to log in. Specify your Confluence Username and Password and click Log in.
Next to the panels toggle button there is a down arrow that opens the menu, where you can select the layout and the action that happens when you click an issue or a page in a structure. If you have Do Nothing option selected, the second panel will not be opened as you click the items in your structure.
You can create new pages in your Confluence right from the Structure page:
As you press it, the New Item panel is shown. The panel allows to create issues, pages and folders. Switch to the Page tab.
If you've been using the full New Issue dialog to create issues, this dialog will be shown as you press Enter. Click the Switch to panel link to switch to the New Item panel.
You can configure some automation rules for pages in your structure in a similar way you do for issues.
You can pull in all child pages of the pages previously added to your structure. To do that you need to switch on the Automation editing mode, select the top-most item that appears at the top of the Structure and then add the Child Pages Extender from the Automation menu.
As you move a child page from one parent page to another in your structure, this page in Confluence will also be moved from one parent page to another. If you want to disable such updates, switch on Automation editing, double-click the Child Pages Extender and select the option for disabling changes via Structure.
If you have links between pages and issues, you can visualise them in Structure too. To pull in pages linked to issues in your structure, add the Linked Pages Extender to your structure. Currently you cannot automatically pull in issues linked to pages in a structure, but this will be added in the future versions.
Moving pages between issues in Structure will update the links. If this undesirable, disable editing via Structure in the Linked Pages Extender settings.