Skip to Content

Wiki source code of Jira

Version 31.1 by Boris Folgmann on 2026/05/08 15:14
Show last authors
1
2
3 {{toc/}}
4
5 = Introduction =
6
7 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.
8
9 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.
10
11 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.
12
13 = First steps in Jira =
14
15 == {{id name="logintojira"/}}Log in to Jira from DevOps Portal ==
16
17 In DevOps Portal sign in to your account with your registered mail and password.
18
19 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/]]
20
21 == {{id name="selectprojectjira"/}}Select Project ==
22
23 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:
24
25 [[image:2.png||height="273" width="535"]]
26
27 By clicking on **Agile Board**, you will be redirected to the selected project’s board in Jira:
28
29 [[image:2.1.png||height="297" width="418"]]
30
31 [[image:2.2.png||height="404" width="977"]]
32
33 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:
34
35 [[image:backlog.png||data-xwiki-image-style-border="true" height="276" width="468"]]
36
37 [[image:backlog-1.png||data-xwiki-image-style-border="true" height="355" width="933"]]
38
39 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):
40
41 [[image:view%20all%20prj.png||alt="view all prj.png" data-xwiki-image-style-border="true" height="281" width="633"]]
42
43 If **View All Projects** is selected, you can see the projects to which you are assigned to.
44
45 [[image:view%20all%20prj-2.png||alt="view all prj-2.png" data-xwiki-image-style-border="true" height="273" width="1002"]]
46
47 You can select the desired project to continue your work.
48
49 = DevOps Jira Agile Board Management =
50
51 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.
52
53 [[image:devops.png||height="402" width="465"]]
54
55 = Boards =
56
57 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:
58
59 * **Scrum board**: For teams that plan their work in sprints. Includes a backlog.
60 * **Kanban board**: For teams that focus on managing and constraining their work-in-progress. Includes the option of a Kanban backlog
61
62 Select the** Boards** tab and select **View all boards**:
63
64 [[image:all%20boards.png||alt="all boards.png" height="135" width="582"]]
65
66 == {{id name="jira_create_boards"/}}Create Boards ==
67
68 {{info}}
69 **Prerequisites**
70
71 1. You are logged in to Jira.
72 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.
73 {{/info}}
74
75 To create a new board click on **Create board** button on the right corner:
76
77 [[image:image2019-9-18_10-41-10.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" height="118" width="700"]]
78
79 Select the type of the new board: it can be **Scrum** or **Kanban** board.
80
81 === Creating a Scrum Board ===
82
83 [[image:image2019-9-18_10-42-48.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" height="249" width="700"]]
84
85 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.
86
87 [[image:image2019-9-18_10-58-28.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" width="700"]]
88
89 Type the **Board Name** and select a **Project(s). **Then click** Create board.**
90
91 In this example the name is //Custom Scrum board// and the selected project is //NEWPROJECT.//
92
93 **[[image:create%20board.png||alt="create board.png" height="356" width="812"]]**
94
95 === Creating a Kanban Board ===
96
97 [[image:1757324747229-442.png||height="304" width="760"]]
98
99 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
100
101 and selecting a project from the drop-down list, we can create the Kanban board:
102
103 [[image:1757325036888-798.png||height="304" width="766"]]
104
105 After creating the board, we will be forwarded to the Kanban board, where we can see the selected project with its created issues.
106
107 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.
108
109 == Manage Boards ==
110
111 {{info}}
112 **Prerequisites**
113
114 1. You are logged in to Jira.
115 1. You have at least ADMIN role on this project to be able to manage boards connected with the project.
116 {{/info}}
117
118 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**:
119
120 [[image:image2019-9-10_11-20-4.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" height="152" width="183"]]
121
122 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.
123
124 [[image:general.png||height="480" width="872"]]
125
126 {{info}}
127 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
128
129 To qualify for a match, the board name has to start with the project key. For example, if the project key is "PKEY":
130
131 * Board names like "PKEY", "PKEY Kanban Board", "PKEY_Team_Board", "PKEY-CoolBoard" etc. will have their Administrators managed by the DevOps Portal
132 * Board names like "_PKEY MyBoard" or "Joe's Board" don't have a "PKEY" prefix. They will not be managed by the DevOps Portal.
133 * 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.
134 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.
135 {{/info}}
136
137 === Configuring Columns of a Board ===
138
139 To Edit the columns of the board (e.g. you would like to create a new column) just click Columns tab on the left.
140
141 In the following example a new column will be added named //Pending//.
142
143 First  a new status can be created by clicking **Add status**:
144
145 [[image:image2019-9-10_11-39-43.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" height="396" width="1100"]]
146
147 In the appearing window type //Blocked// for the name than click **Add** to create a new status.
148
149 [[image:image2019-9-10_11-56-24.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" height="205" width="461"]]
150
151 Then the new column can be created by clicking **Add column**:
152
153 [[image:image2019-9-10_11-58-34.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" height="498" width="1100"]]
154
155 In the appearing window type //Blocked// for the name than click **Add** to create a new column.
156
157 [[image:image2019-9-10_12-1-13.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" height="218" width="483"]]
158
159 Now the new column with a new status has been created:
160
161 [[image:image2019-9-10_12-2-2.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" height="454" width="1100"]]
162
163 You can also change the columns order with a drag and drop method.
164
165 === Configuring Swimlanes ===
166
167 To configure the rows (to group issues) click **Swimlanes** on the left then select from** Base Swimlanes** on:
168
169 [[image:image2019-9-10_14-2-23.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" height="434" width="1100"]]
170
171 === Configuring quick filters ===
172
173 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:
174
175 [[image:image2019-9-10_11-48-1.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" height="273" width="1100"]]
176
177 === Other Configuration Options ===
178
179 You can set the design of the board by changing settings in** Card colors** or **Card layout**
180
181 **Estimation** can be based on //Story Points//, //Original Time Estimate//, or //Issue Count.//
182
183 You can set the **Working days **also (by default it is Monday-Friday)
184
185 You can customize the issue's appearance in **Issue Detail View.**
186
187 == Change the Project Lead in Jira ==
188
189 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**:
190
191 [[image:image2019-9-4_11-36-39.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" height="204" width="450"]]
192
193 Now as the example shows Barney Rubble is the //Project Lead//, and this user will be the //Default Assignee// of the created issues:
194
195 [[image:image2019-9-4_11-38-46.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" height="133" width="450"]]
196
197 == Manage Users and Roles ==
198
199 Open your project, click on **Project settings icon** in the bottom-left corner of Jira**.**
200
201 Select **Users and roles** on the left menu and you can see the users and groups with the assigned roles:
202
203 [[image:image2019-9-4_11-27-48.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" height="661" width="1100"]]
204
205 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.
206
207 = View Project Permissions =
208
209 Click on** Permissions **as seen below view the permissions of the 4 project roles:
210
211 [[image:image2019-9-11_10-41-21.png||data-xwiki-image-style-border="true" height="605" width="1100"]]
212
213 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/]]
214
215 = Links to Jira vendor documentation =
216
217 * [[Scrum Guide>>https://www.atlassian.com/agile/scrum]]
218 * [[Kanban Guide>>https://www.atlassian.com/agile/kanban]]
219 * [[Agile Epic and user stories>>https://www.atlassian.com/agile/project-management/epics-stories-themes]]
220 * [[Jira Board>>https://www.atlassian.com/software/jira/guides/boards/overview#what-is-a-jira-board]]
221 * [[Jira Work Items/Issues>>https://www.atlassian.com/software/jira/guides/issues/overview#what-is-jira-work%20item-hierarchy]]
222
223
© 2018-2026 T-Systems International GmbH