Wiki source code of Confluence
Last modified by Boris Folgmann on 2026/05/08 15:57
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | |||
| 2 | |||
| 3 | {{toc/}} | ||
| 4 | |||
| 5 | = Introduction = | ||
| 6 | |||
| 7 | DevOps-as-a-Service can include a hosted and managed version of Atlassian Confluence.This document describes the important features of DevOps-as-a-Service concerning Confluence. For general concepts and details about Confluence, please refer to the **Confluence vendor documentation **section at the end of this document. | ||
| 8 | |||
| 9 | = First steps in Confluence = | ||
| 10 | |||
| 11 | == Log in to Confluence from DevOps Portal == | ||
| 12 | |||
| 13 | In DevOps Portal sign in to your account with your registered mail and password. | ||
| 14 | |||
| 15 | For more information about log in to DevOps Portal see [[DevOps Portal for Users>>path:https://prd.sdc.t-systems.net/xwiki/wiki/devopsaas/view/DevOps%20Portal%20for%20Users/]]. | ||
| 16 | |||
| 17 | == Select Project == | ||
| 18 | |||
| 19 | After successful authentication, you will be directed to the DevOps Portal, in this example the user is assigned to two projects, and the user has a specific role in each project. By selecting the relevant Project from the drop-down list, you can navigate through the **Collaboration and Documentation** under **Confluence **section as shown in below example: | ||
| 20 | |||
| 21 | [[image:3.png||height="307" width="874"]] | ||
| 22 | |||
| 23 | = Create a page = | ||
| 24 | |||
| 25 | If you want to create a page, then you will find a button on the top of the page. Here you can select to create a page (enough to click on the Create button), but you can create other type of pages as well, if you press the "..." instead. | ||
| 26 | |||
| 27 | [[image:1768306913775-637.png]] | ||
| 28 | |||
| 29 | [[image:1768307002777-694.png||height="297" width="550"]] | ||
| 30 | |||
| 31 | = Link a Jira issue into the page content = | ||
| 32 | |||
| 33 | If you would like to insert a link to a Jira ticket in your page content (at first you have to create the exact ticket), click on the **Insert macros** button and select **Jira Issue/Filter:** | ||
| 34 | [[image:image2019-8-6_11-49-3.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" width="1109"]] | ||
| 35 | |||
| 36 | Type the ticket's name (key or summary) on the top (in this example the //Deploy microservices// ticket can be inserted), then click **Insert** at the bottom: | ||
| 37 | |||
| 38 | [[image:image2019-8-6_11-50-11.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" width="700"]] | ||
| 39 | |||
| 40 | To see the result, you have to **Publish** the page. | ||
| 41 | |||
| 42 | [[image:image2019-8-6_11-56-19.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" width="1109"]] | ||
| 43 | |||
| 44 | Now the link to the ticket is created and the //status// of the ticket (in the example it is IN PROGRESS) is shown. Clicking the link will open the ticket in Jira. | ||
| 45 | |||
| 46 | [[image:image2019-8-6_11-59-39.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" width="1109"]] | ||
| 47 | |||
| 48 | If the //status of the ticket changes//, this will be reflected in the Confluence page (in this example the ticket status is changed to DONE). | ||
| 49 | |||
| 50 | [[image:image2019-8-6_12-2-51.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" width="1109"]] | ||
| 51 | |||
| 52 | The created page can be seen on the left side under **PAGE TREE** (which represents the hierarchy of the created pages also) | ||
| 53 | |||
| 54 | [[image:image2019-8-6_12-11-6.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" width="500"]] | ||
| 55 | |||
| 56 | {{info}} | ||
| 57 | You can create other pages by repeating this method (create, then publish). | ||
| 58 | {{/info}} | ||
| 59 | |||
| 60 | = Table of Contents = | ||
| 61 | |||
| 62 | If you would like to add a table of contents to your page, at first you have to create the titles by selecting one of the Heading formats for the text: | ||
| 63 | |||
| 64 | [[image:image2019-8-6_14-28-0.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" width="1109"]] | ||
| 65 | |||
| 66 | Then click **Insert macros** icon and select **Table of Contents**. | ||
| 67 | |||
| 68 | [[image:image2019-8-6_14-28-48.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" width="1109"]] | ||
| 69 | |||
| 70 | A dialog pops up that let's you customize certain aspects of the table of contents (in this example nothing is changed). Click **Insert** once you're done: | ||
| 71 | |||
| 72 | [[image:image2019-8-6_14-30-4.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" width="900"]] | ||
| 73 | |||
| 74 | Now the **Table of Contents** macro appears at the last cursor position on the page: | ||
| 75 | |||
| 76 | [[image:image2019-8-6_14-32-14.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" height="543" width="500"]] | ||
| 77 | |||
| 78 | To check the macro simply **Update** the page and the Table of contents is created from your page's headings: | ||
| 79 | |||
| 80 | [[image:image2019-8-6_14-36-21.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" height="502" width="500"]] | ||
| 81 | |||
| 82 | = DevOps Toolchain = | ||
| 83 | |||
| 84 | As it is shown in the picture below, by clicking on the dots icon in the top left corner you can have quick access to the other tools in your DevOps-as-a-Service instance. | ||
| 85 | |||
| 86 | [[image:devops%20prd.png||alt="devops prd.png"]] | ||
| 87 | |||
| 88 | {{info}} | ||
| 89 | **Automatic project linking across Atlassian tools:** | ||
| 90 | Jira, Confluence, and Bitbucket projects with the same Project Key are now automatically linked via the DevOps Portal. This simplifies workflows, such as selecting a Git repository in Bitbucket when creating a branch for a Jira issue. Previously, this required Sysadmin privileges, but the Portal now handles it automatically. To activate for an existing project, simply **Edit and Save** or **Resync** the project. | ||
| 91 | {{/info}} | ||
| 92 | |||
| 93 | {{info}} | ||
| 94 | **Automated deletion of personal Confluence Spaces:** | ||
| 95 | When a locked user is deleted in the DevOps Portal, any personal Confluence spaces associated with that user will be automatically removed. | ||
| 96 | {{/info}} | ||
| 97 | |||
| 98 | [[image:1757581866568-620.png]] | ||
| 99 | |||
| 100 | = Links to Confluence vendor documentation = | ||
| 101 | |||
| 102 | Please check out the [[vendor provided documentation>>url:https://confluence.atlassian.com/confcloud]] or [[Getting Started with Confluence>>https://www.atlassian.com/software/confluence/resources/guides/confluence-essentials/navigate#home-and-main-page]] to learn how to work in Confluence. You can skip any documentation related to Confluence installation or administration. | ||
| 103 | |||
| 104 |