Wiki source code of Jira

Last modified by Boris Folgmann on 2026/05/08 15:42

Hide last authors
DOaaS Operator 1.1 1 {{toc/}}
2
Boris Folgmann 31.1 3 = Introduction =
DOaaS Operator 1.1 4
Boris Folgmann 31.1 5 This document describes the important features of DevOps-as-a-Service concerning Jira. For general concepts and details about Jira, please refer to the **Jira vendor documentation **section at the end of this document.
DOaaS Operator 1.1 6
Boris Folgmann 31.1 7 Project admins can edit and save their projects in the DevOps Portal. This can be used to change the name or description of a project. The change is automatically propagated to all tools including Jira.
DOaaS Operator 1.1 8
Boris Folgmann 31.1 9 A custom Jira plugin automatically removes unused screens, screen schemes, and issue-type screen schemes whenever the DevOps Portal deletes a project, helping to free up resources and improve performance.
DOaaS Operator 1.1 10
Boris Folgmann 31.1 11 = First steps in Jira =
DOaaS Operator 1.1 12
Boris Folgmann 31.1 13 == {{id name="logintojira"/}}Log in to Jira from DevOps Portal ==
DOaaS Operator 1.1 14
Boris Folgmann 31.1 15 In DevOps Portal sign in to your account with your registered mail and password.
DOaaS Operator 1.1 16
Boris Folgmann 33.1 17 For more information about logging in to DevOps Portal see [[DevOps Portal for Users>>https://prd.sdc.t-systems.net/xwiki/wiki/devopsaas/view/DevOps%20Portal%20for%20Users/]].
DOaaS Operator 1.1 18
Boris Folgmann 31.1 19 == {{id name="selectprojectjira"/}}Select Project ==
DOaaS Operator 1.1 20
Boris Folgmann 31.1 21 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:
DOaaS Operator 1.1 22
Boris Folgmann 31.1 23 [[image:2.png||height="273" width="535"]]
DOaaS Operator 1.1 24
Boris Folgmann 31.1 25 By clicking on **Agile Board**, you will be redirected to the selected project’s board in Jira:
DOaaS Operator 1.1 26
Boris Folgmann 31.1 27 [[image:2.1.png||height="297" width="418"]]
DOaaS Operator 1.1 28
Boris Folgmann 31.1 29 [[image:2.2.png||height="404" width="977"]]
DOaaS Operator 1.1 30
Boris Folgmann 31.1 31 The next option shows the **Backlog**, where the created issues will appear. If you are the first user to create an issue, the Backlog will be empty:
DOaaS Operator 1.1 32
Boris Folgmann 31.1 33 [[image:backlog.png||data-xwiki-image-style-border="true" height="276" width="468"]]
DOaaS Operator 1.1 34
Boris Folgmann 31.1 35 [[image:backlog-1.png||data-xwiki-image-style-border="true" height="355" width="933"]]
DOaaS Operator 1.1 36
Boris Folgmann 31.1 37 If you would like to create or view issues belonging to other projects you can select the project by clicking **Projects** on the top. In this example you can see the current project (NEWPROJECT):
DOaaS Operator 1.1 38
Boris Folgmann 31.1 39 [[image:view%20all%20prj.png||alt="view all prj.png" data-xwiki-image-style-border="true" height="281" width="633"]]
DOaaS Operator 1.1 40
Boris Folgmann 31.1 41 If **View All Projects** is selected, you can see the projects to which you are assigned to.
DOaaS Operator 1.1 42
Boris Folgmann 31.1 43 [[image:view%20all%20prj-2.png||alt="view all prj-2.png" data-xwiki-image-style-border="true" height="273" width="1002"]]
DOaaS Operator 1.1 44
45 You can select the desired project to continue your work.
46
Boris Folgmann 31.1 47 = DevOps Jira Agile Board Management =
DOaaS Operator 1.1 48
Boris Folgmann 31.1 49 As it is shown in the picture below, by clicking on the dots menu in the top left corner of Jira, you have quick access to all tools which are part of your the DevOps-as-a-Service instance.
DOaaS Operator 1.1 50
Boris Folgmann 31.1 51 [[image:devops.png||height="402" width="465"]]
DOaaS Operator 1.1 52
53 = Boards =
54
55 A board displays issues from one or more projects, giving you a flexible way of viewing, managing, and reporting on work in progress. The available types of boards in Jira are:
56
57 * **Scrum board**: For teams that plan their work in sprints. Includes a backlog.
58 * **Kanban board**: For teams that focus on managing and constraining their work-in-progress. Includes the option of a Kanban backlog
59
60 Select the** Boards** tab and select **View all boards**:
61
Boris Folgmann 31.1 62 [[image:all%20boards.png||alt="all boards.png" height="135" width="582"]]
DOaaS Operator 1.1 63
64 == {{id name="jira_create_boards"/}}Create Boards ==
65
66 {{info}}
67 **Prerequisites**
68
69 1. You are logged in to Jira.
Boris Folgmann 31.1 70 1. You can create new boards, but you must have at least a VIEWER role on the project for which you want to create a board to see the issues.
DOaaS Operator 1.1 71 {{/info}}
72
73 To create a new board click on **Create board** button on the right corner:
74
Boris Folgmann 31.1 75 [[image:image2019-9-18_10-41-10.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" height="118" width="700"]]
DOaaS Operator 1.1 76
Boris Folgmann 31.1 77 Select the type of the new board: it can be **Scrum** or **Kanban** board.
DOaaS Operator 1.1 78
Boris Folgmann 31.1 79 === Creating a Scrum Board ===
DOaaS Operator 1.1 80
Boris Folgmann 31.1 81 [[image:image2019-9-18_10-42-48.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" height="249" width="700"]]
DOaaS Operator 1.1 82
Boris Folgmann 31.1 83 In this example a Scrum board has been selected and there is an option to create a **Board from an existing project** or from an existing Saved Filter.
84
85 [[image:image2019-9-18_10-58-28.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" width="700"]]
86
DOaaS Operator 1.1 87 Type the **Board Name** and select a **Project(s). **Then click** Create board.**
88
Boris Folgmann 31.1 89 In this example the name is //Custom Scrum board// and the selected project is //NEWPROJECT.//
DOaaS Operator 1.1 90
Boris Folgmann 31.1 91 **[[image:create%20board.png||alt="create board.png" height="356" width="812"]]**
DOaaS Operator 1.1 92
Boris Folgmann 31.1 93 === Creating a Kanban Board ===
DOaaS Operator 1.1 94
Boris Folgmann 31.1 95 [[image:1757324747229-442.png||height="304" width="760"]]
DOaaS Operator 1.1 96
Boris Folgmann 31.1 97 In this example the Kanban board has been selected and created as** **an** existing project** like the above example. In the next step, after naming the board
DOaaS Operator 1.1 98
Boris Folgmann 31.1 99 and selecting a project from the drop-down list, we can create the Kanban board:
100
101 [[image:1757325036888-798.png||height="304" width="766"]]
102
103 After creating the board, we will be forwarded to the Kanban board, where we can see the selected project with its created issues.
104
105 The difference between Kanban and Scrum is that Scrum uses sprints with defined meetings, a fixed set of tasks in a fixed period of time (typically e2 weeks). Kanban on the other hand, is an ongoing process. Scrum boards will be changed/updated after each sprint, but Kanban boards are continuously updated throughout a project and are more flexible.
106
DOaaS Operator 1.1 107 == Manage Boards ==
108
109 {{info}}
110 **Prerequisites**
111
112 1. You are logged in to Jira.
Boris Folgmann 31.1 113 1. You have at least ADMIN role on this project to be able to manage boards connected with the project.
DOaaS Operator 1.1 114 {{/info}}
115
Boris Folgmann 31.1 116 Click the **Board menu** (3 dots on the right)  of the selected board. You can **Copy** or **Delete** the board, and you can also modify the default settings by selecting **Configure**:
DOaaS Operator 1.1 117
Boris Folgmann 31.1 118 [[image:image2019-9-10_11-20-4.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" height="152" width="183"]]
DOaaS Operator 1.1 119
Boris Folgmann 31.1 120 The //**General**// information of the board appears, containing the //board's name//, the //administrator(s)// and the //filter// which defines what issues are visualized in the board.
DOaaS Operator 1.1 121
Boris Folgmann 31.1 122 [[image:general.png||height="480" width="872"]]
DOaaS Operator 1.1 123
Boris Folgmann 31.1 124 {{info}}
125 In DevOps Portal, each time a project is resynced or an Admin is modified (added or deleted), the DevOps platform will align the Administrators of the corresponding boards to the list of Project Admins
DOaaS Operator 1.1 126
Boris Folgmann 31.1 127 To qualify for a match, the board name has to start with the project key. For example, if the project key is "PKEY":
DOaaS Operator 1.1 128
Boris Folgmann 31.1 129 * Board names like "PKEY", "PKEY Kanban Board", "PKEY_Team_Board", "PKEY-CoolBoard" etc. will have their Administrators managed by the DevOps Portal
130 * Board names like "_PKEY MyBoard" or "Joe's Board" don't have a "PKEY" prefix. They will not be managed by the DevOps Portal.
131 * If no boards were created manually, no changes are needed, as “PKEY” is the default name for automatically created boards. These boards will continue to be recognized and managed by DevOps Portal as before.If any boards were created manually, please review their names and rename them as necessary to ensure the desired behavior.
132 Because board administrators have the ability to rename their boards, each administrator can choose whether to keep a board managed by DevOps Portal or convert it into an independent board where the list of administrators is maintained manually in Jira.
133 {{/info}}
134
DOaaS Operator 1.1 135 === Configuring Columns of a Board ===
136
137 To Edit the columns of the board (e.g. you would like to create a new column) just click Columns tab on the left.
138
139 In the following example a new column will be added named //Pending//.
140
141 First  a new status can be created by clicking **Add status**:
142
Boris Folgmann 31.1 143 [[image:image2019-9-10_11-39-43.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" height="396" width="1100"]]
DOaaS Operator 1.1 144
145 In the appearing window type //Blocked// for the name than click **Add** to create a new status.
146
Boris Folgmann 31.1 147 [[image:image2019-9-10_11-56-24.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" height="205" width="461"]]
DOaaS Operator 1.1 148
149 Then the new column can be created by clicking **Add column**:
150
Boris Folgmann 31.1 151 [[image:image2019-9-10_11-58-34.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" height="498" width="1100"]]
DOaaS Operator 1.1 152
153 In the appearing window type //Blocked// for the name than click **Add** to create a new column.
154
Boris Folgmann 31.1 155 [[image:image2019-9-10_12-1-13.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" height="218" width="483"]]
DOaaS Operator 1.1 156
157 Now the new column with a new status has been created:
158
Boris Folgmann 31.1 159 [[image:image2019-9-10_12-2-2.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" height="454" width="1100"]]
DOaaS Operator 1.1 160
161 You can also change the columns order with a drag and drop method.
162
163 === Configuring Swimlanes ===
164
165 To configure the rows (to group issues) click **Swimlanes** on the left then select from** Base Swimlanes** on:
166
Boris Folgmann 31.1 167 [[image:image2019-9-10_14-2-23.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" height="434" width="1100"]]
DOaaS Operator 1.1 168
169 === Configuring quick filters ===
170
171 You can set custom filter tabs for the board - in this example a new tab named Max Mustermann is created, and by clicking this tab only the user's issues visible:
172
Boris Folgmann 31.1 173 [[image:image2019-9-10_11-48-1.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" height="273" width="1100"]]
DOaaS Operator 1.1 174
175 === Other Configuration Options ===
176
177 You can set the design of the board by changing settings in** Card colors** or **Card layout**
178
179 **Estimation** can be based on //Story Points//, //Original Time Estimate//, or //Issue Count.//
180
181 You can set the **Working days **also (by default it is Monday-Friday)
182
183 You can customize the issue's appearance in **Issue Detail View.**
184
Boris Folgmann 31.1 185 == Change the Project Lead in Jira ==
DOaaS Operator 1.1 186
Boris Folgmann 31.1 187 Select the user who would be the **Project Lead **on the top (in this example Barney Rubble), and change the **Default Assignee** to Project Lead, then click **Update**:
DOaaS Operator 1.1 188
Boris Folgmann 31.1 189 [[image:image2019-9-4_11-36-39.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" height="204" width="450"]]
DOaaS Operator 1.1 190
Boris Folgmann 31.1 191 Now as the example shows Barney Rubble is the //Project Lead//, and this user will be the //Default Assignee// of the created issues:
DOaaS Operator 1.1 192
Boris Folgmann 31.1 193 [[image:image2019-9-4_11-38-46.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" height="133" width="450"]]
DOaaS Operator 1.1 194
Boris Folgmann 31.1 195 == Manage Users and Roles ==
DOaaS Operator 1.1 196
Boris Folgmann 31.1 197 Open your project, click on **Project settings icon** in the bottom-left corner of Jira**.**
DOaaS Operator 1.1 198
199 Select **Users and roles** on the left menu and you can see the users and groups with the assigned roles:
200
Boris Folgmann 31.1 201 [[image:image2019-9-4_11-27-48.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" height="661" width="1100"]]
DOaaS Operator 1.1 202
Boris Folgmann 31.1 203 As a project admin you can change the role assignments here, but please note that if you trigger a "Resync project and roles" in the DevOps Portal, it will reset the roles to exactly what has been defined in the Portal. Therefore changes here, make most sense for temporarily exceptions for certain user, e.g. to raise their possibilities for a limited amount of time.
DOaaS Operator 1.1 204
Boris Folgmann 31.1 205 = View Project Permissions =
DOaaS Operator 1.1 206
Boris Folgmann 31.1 207 Click on** Permissions **as seen below view the permissions of the 4 project roles:
DOaaS Operator 1.1 208
Boris Folgmann 31.1 209 [[image:image2019-9-11_10-41-21.png||data-xwiki-image-style-border="true" height="605" width="1100"]]
DOaaS Operator 1.1 210
Boris Folgmann 31.1 211 For more details refer to [[Users and roles>>https://prd.sdc.t-systems.net/xwiki/wiki/sdcloud/view/DRAFT%20DevOps%20Portal%20for%20Creators%20and%20Admins/Users%20and%20roles/]]
DOaaS Operator 1.1 212
Boris Folgmann 31.1 213 = Links to Jira vendor documentation =
DOaaS Operator 1.1 214
Boris Folgmann 31.1 215 * [[Scrum Guide>>https://www.atlassian.com/agile/scrum]]
216 * [[Kanban Guide>>https://www.atlassian.com/agile/kanban]]
217 * [[Agile Epic and user stories>>https://www.atlassian.com/agile/project-management/epics-stories-themes]]
218 * [[Jira Board>>https://www.atlassian.com/software/jira/guides/boards/overview#what-is-a-jira-board]]
219 * [[Jira Work Items/Issues>>https://www.atlassian.com/software/jira/guides/issues/overview#what-is-jira-work%20item-hierarchy]]
DOaaS Operator 1.1 220
221