1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
|
'def title Cards - How to use Jira
'def desc Each issue is represented as an object with properties. More specifically, these objects are called 'cards'.
# {title}
{pagenav 4 min;24 July 2020;03 June 2021}
{pagination ./;Filters;./filters.html;Projects;./projects.html}
.contents
.numbered
1. {uhref Properties}
2. {uhref Creating}
3. {uhref Viewing}
4. {uhref How to use}
.numbered
1. {uhref Right side}
2. {uhref Work log}
3. {uhref Issue flagging}
4. {uhref Basic issue information}
{b Each issue is represented as an object with properties}. More specifically, these objects are called 'cards'.
{img ./img/kanban-cards.png}
## Properties
Each card has the following properties:
{img ./img/fields-cards.png}
:unordered
- {b Project} - the {url project;./projects.html} this card is stored in
{img ./img/project-create-card.png}
- {b Issue type} - the basic purpose of an issue (Improvement, Bug, ...)
{img ./img/issue-types.png}
:bulleted
- {img Story;./img/story-type.png} - functionality or feature expressed as a goal, something like "As a user, I want to be able to pay for my order via PayPal"
- {img Bug;./img/bug-type.png} - a problem/error
- {img Epic;./img/epic-type.png} - a collection of issues, issues are linked through 'Epic link' (see below)
- {img Task;./img/task-type.png} - a small piece of work
- {img Sub-task;./img/sub-task-type.png} - an issue that is directly connected to another issue. This is used for when a given issue needs to be broken down into separate even smaller issues.
- {b Summary} - a (required) brief explanation of the issue
{img ./img/summary-create-card.png}
- {b Description} - detailed explanation of the issue
{img ./img/description-create-card.png}
- {b Reporter} - person who created the issue
{img ./img/reporter-create-card.png}
- {b Assignee} - person who will work on the issue
{img ./img/assignee-create-card.png}
- {b Labels} - tags with which you can organise even more the issue
{img ./img/label-create-card.png}
- {b Epic link} - link of issue with type Epic
{img ./img/epic-link-create-card.png}
## Creating
To create a card yourself, you need to {b press the {` Create} button on the top bar}.
{img ./img/create-header.png}
## Viewing
{b All} cards (issues) can be viewed from a {url project;./projects.html}'s side menu, under 'Issues'.
{img ./img/issues-sidebar.png}
Of course, they can also be viewed through {b {url filters;./filters.html}} and a {b {url project;./projects.html}'s board}.
## How to use
By default, opening a card presents, at the top, it's {b key} (think of it as an ID),
{img ./img/card-key.png}
it's {b summary} below it,
{img ./img/card-summary.png}
options for adding {b attachments}, {b subtasks}, {b linking issues} and {b adding more apps} (think of apps like extensions),
{img ./img/card-attach-subtask.png}
following are the {b description}, {b actual attachments}, {b subtasks}, {b linked issues}, etc.,
{img ./img/desc-att-sub-link.png}
and at the bottom you have the {b activity}, consisting of {b comments} on the issue,
{img ./img/activity-comments.png}
{b history} of things that have happened to that issue,
{img ./img/activity-history.png}
and {b work logs} (a bit later we talk about them in more detail).
{img ./img/activity-work-log.png}
### Right side
To the right side, you have all of the different {b properties} (some fields without a value will be hidden).
{img ./img/card-right-side.png}
On the top right you can change {b watch options} ({url watching an issue;https://www.idalko.com/jira-watch-issues/} means you get notified by all changes done to it), you can {b share} the card and do {b actions} (the three dots).
{img ./img/card-top-right.png}
{b Actions} are things you can do to the whole card, like moving or deleting it.
{img ./img/card-actions.png}
The most notable options are {` {url Log work;https://confluence.atlassian.com/jirasoftwarecloud/logging-work-on-issues-902499028.html}} and {` Add flag}.
### Work log
In Jira, you can {b estimate how long an issue will take for it to be resolved}. This is done through {b logging work}.
In the {` Log work} screen, you'll be met with a {` Time spent} and {` Time remaining} fields, that you'll need to fill with the appropriate information.
{img ./img/time-tracking.png}
The time remaining takes a {b default} value from the {b previous time log}, so you don't need to specify it every time.
### Issue flagging
A {b flagged issue} is an issue that is very important. Flagged issues are displayed in yellow to signify their needed attention.
{img ./img/flagged-card.png}
### Basic issue information
On the bottom right you can see {b when the issue was created} and {b when it was last updated}. You can also access the field configuration menu from the {` Configure} button. It won't be covered in this tutorial, you can read about it {url here;https://confluence.atlassian.com/adminjiracloud/changing-a-field-configuration-844500798.html}.
{img ./img/time-and-configure.png}
|
