Confluence is a business wiki used for documentation and project planning, either cloud or self-hosted, from Atlassian, the creators of JIRA and several other products. For further information about the features and capabilities of Confluence please visit the Atlassian website.
The integration with dynaBOARD allows the following features:
In order to connect dynaBOARD with Confluence, you need the following:
The setup in Confluence is very easy. You need a Confluence user which has only read rights. You can choose a user which has also creating/editing rights, but this is not necessary at the moment.
In the future we might add functions to the Confluence integration which demand more rights, but currently reading rights is sufficient.
Log in to dynaBOARD (with your partner user, not the admin user), and go to Settings. Then click on the tab Confluence.
Select "active" under Confluence Integration. Several fields and options will now show up.
Enter the following information into the fields:
If you want to connect to Confluence cloud (not server version), please add the following at the end of the url:
This is needed for the API path, so for example if your Confluence url is
into the url field.
After that, click on Save. If all works well, you should get a positive response.
Proceed to "Settings", below.
If an error occurs during connection setup, please check the following before contacting our support team:
There are no specific settings in this area for the integration.
To allow a customer to see the document menu tab, and assign documents from Confluence to him, head over to Customers. Once set up there, a new menu item will appear for the customer users on the left hand, named "Documents". See the User Guide for a description of this page.
The pages from Confluence will be delivered on-demand as a stripped-down HTML page, provided by Confluence API. The pages in dynaBOARD will look a bit tuned down compared to the ones in Confluence, as the styling in both systems are different. The content, thought, stays mostly unchanged - with the following exceptions:
All links will be analyzed. If it is an external link (i.e. destination is a regular website, but not Confluence or JIRA), it remains unchanged.
If the link is a Confluence link, dynaBOARD will try to convert it to a link through which the content will be displayed in dynaBOARD when clicked on it - redirecting your customers to Confluence would not be desirable, as they usually do not have access to it (apparently, as you are using dynaBOARD for sharing documents with them). dynaBOARD will check if the destination page is allowed for the customer to view - if you made it accessible on the customer editing page, it will be linked. If not, the link will remain, but clicking on it will do nothing.
If the link is a JIRA link (i.e. the base url is the same as the JIRA instance you connected dynaBOARD to), it will convert the link to a view issue link for dynaBOARD. If the customer does not have access to the project associated with the issue, he will get a message once he clicks on it.
Dynamic fields (e.g. search form fields) will be removed, if possible, or remain without function. This also relates to issue lists from JIRA, which are generated dynamically on-demand - unfortunately the Confluence API does not deliver them.
Regular images should be displayed as expected, if not provided by some addon through external sources.
As you can see, it is advisable to avoid some elements (e.g. forms or dynamic issue tables) in the pages you want to provide to your customers, as they will not be displayed properly or will not function as expected.
Things you should know about the integration:
If you are having trouble connecting to your Confluence instance, please check the following: