Connect Confluence with All Quiet for streamlined post-incident analysis.

​

Create Outbound Integration

1. Click on Integrations > Outbound to navigate to the outbound integrations page.
2. Once you’re on the Outbound Integrations page, click on Create New Integration in the top-right corner.

1. Enter a name for your integration in the Display Name field, such as “Confluence”.
2. Select the team you want to add the integration to.
   For Organizations with Pro and Enterprise plan: This is going to be the root team of your integration. You will be able to add additional teams in the next step.
3. In the Type section, choose Confluence from the dropdown menu.
4. After filling in all required details, click on the Create Outbound Integration button to finalize the setup.

​

Add All Quiet to your Confluence Space

Once you’ve successfully created your new outbound integration, you’ll automatically be redirected to its details page.

1. The option Triggers Only on Forwarded is enabled by default. This means, that we will not automatically forward incidents to create pages in your Confluence space. Pages will only be created if users manually forward specific incidents or if you set up adavnced routing rules for your Confluence integration that automatically forward incidents in specific scenarios. If you disable Triggers Only on Forwarded, we will forward all incidents to Confluence.
   You can change your selection anytime, but we recommend to select Trigger Only When Forwarded. We will explain why in the example below.
2. Only for Pro and Enterprise plan: The root team is pre-selected, and you can add the integration to further teams within the root team’s organization. Team Administrators can add / remove those teams they are an admin in, Organization Administrators & Organization Owners can manage the connections to all teams of the organization.
3. Observe that the installation status of the All Quiet integration is still pending.
4. To complete the integration with your Confluence site, click Add to Confluence.

You’ll be redirected to Confluence, where you’ll have to login first.

After login, you you’ll need to grant All Quiet permissions for your the Confluence site. We request only the permissions essential for All Quiet to operate correctly. These permissions are utilized solely when you interact with the app and are never used for any other purpose.

1. If your Atlassian account is linked to more than one Confluence site, select the site you want to connect All Quiet to.
2. Click Accept.

Then, your are redirected back to your Confluence integration’s details page in All Quiet. Next, you need to configure the integration.

1. As you can see, the Installation Status changed to installed.
2. Select the Confluence Site you want to forward the All Quiet incidents to. You can only select those sites that you granted All Quiet permission to (see prior step).
3. Select the Confluence space in which you want to create pages based on All Quiet incidents.
4. Select the Parent Page for the your incidents’ Confluence pages.
5. Make sure to Save Confluence Settings, otherwise forwarding will not work.

​

Creating an Incident Retro Page in Confluence

In the following part, we want to quickly demonstrate how a Confluence page created from an incident can look like.

In the screenshot below, you can find an All Quiet incident.

1. There was some communication going on, and the team agreed to have a Retro for this incident. That’s why Mads forwarded it to Confluence.
2. The Confluence page is linked.

Following the Link to Confluence, you will see this:

1. As defined in my integration’s settings, the page got created below Parent Page “All Quiet Incident Retros”
2. The title of the Confluence page is a combination of the timestamp of the incident’s creation and the incident title in All Quiet. Please note that timestamps in the title will always be based on your team’s timezone.
3. In this section, you will find the main incident details, as well as a link to the incident in All Quiet (see section headline).
4. This part features all additional incident attributes you previously defined in our mapping engine. Moreover, if there are further links related to the incident, they will be listed here.
5. All events linked to the incident. Basically the communication in All Quiet.
6. The team members that were on-call during each event. Only Tier 1 members and members from higher Tiers that got notified due to escalations are listed.
   As the Confluence page is a snapshot of the All Quiet incident, we recommend to activate the Trigger Only When Forwarded feature for your Confluence integration. That is because when deciding to automatically create the page with incident creation, there won’t be a lot history / events available.