To make it possible to publish your release notes supporting the new Confluence editor, we developed a new Confluence app called https://marketplace.atlassian.com/apps/1230896/arn-confluence-helper-app?hosting=cloud&tab=overview . This is a free app for both paid app and free
| Note |
|---|
If you have not integrated Confluence with ARN yet read Setting up Confluence and follow all the steps. |
Connecting Helper app with ARN
If you have already integrated Confluence with ARN as mentioned above, follow the below steps to complete the setup to publish release notes with the new Confluence editor.
| Note |
|---|
Following above steps helps you integrate Confluence with ARN. Follow below two steps to make sure you are enabling ARN to create Confluence templates with new editor. |
Install ARN Confluence Helper App with your Automated Release Notes
As Confluence administrator, navigate to Manager apps settings within your Confluence Apps menu
Click on Find new apps / Manage apps
Search for ARN Confluence Helper App
Install the app
Establish the Jira and Confluence connection for ARN Confluence Helper App
Create token within Jira
| Note |
|---|
Please note that when the token is generated for this integration using certain user’s Atlassian (Jira) login, in that case ARN allows other users to search project in the capacity of the user whose credetials are used to create the token. For eg. User A’s credetials are used to create token to establish the connection between ARN and Helper app. User B is when searching for different projects/issues, they can see the Jira projects names/issues in the drop down in JQLs sections even if they have no access to all projects that user A has access to. It does not provide a full access, its just visible in doropdown while setting up JQL within JQL sections and they could be aware of all projects or issues avaiable in Jira. Due to some technical limitations we are still investigating this issue. We intend to resolve this but we have no ETA on when this will be resolved. |
Go to App Menu from Jira settings >> Configurations under Automated Release Notes section >> Integrations tab >> click on Create Token under Confluence integration section
If you have integrated multiple Confluence instances with ARN, please make sure you are generating the token for the relevant Confluence instance where you have the ARN Confluence Helper App installed.
Now copy the created token
| Note |
|---|
|
Copy token in Confluence’s configurations section
Go to Manage apps in Confluence >> click on ARN Confluence Helper App under Configurations
Click on Add Token & paste the token that was copied from Jira’s ARN configurations and click on Save.
| Note |
|---|
This step establishes a connection beeween Conflunce, Jira and ARN. If you do not follow this step, ARN Confluence Helper will still work and you will be able to use this feature. However, that will not allow you to have easy JQL suggesstions while creating Confluence templates and it is quite error prone unless you are sure the JQLs that you are adding is 100% correct. To avoid any such issues, it is recommeded to complete this step More details in below section. |
| Info |
|---|
If you have already added a token before and want to update it, you can regenerate the token from Jira ARN configuration and update it within helper app configuration under Conflunce. Follow the same navigations explained above. |
Once you have completed this, you are all set to publish release notes with the new Confluence editor, below are the steps -
On this page | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
| Iframe | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
