# Cards - How to use Jira

'define expected-reading 4 min
'define created 24 July 2020
'define edited 03 June 2021
[$pagenav]

'define start_link ./
'define prev_link ./filters.html Filters
'define next_link ./projects.html Projects
[$pagination_middle]

.contents
.numbered
1. [url #properties Properties]
2. [url #creating Creating]
3. [url #viewing Viewing]
4. [url #how-to-use How to use]
   .numbered
   1. [url #right-side Right side]
   2. [url #work-log Work log]
   3. [url #issue-flagging Issue flagging]
   4. [url #basic-issue-information Basic issue information]

[=Each issue is represented as an object with properties=]. More specifically, these objects are called 'cards'.

[image ./img/kanban-cards.png]

## Properties

Each card has the following properties:

[image ./img/fields-cards.png]

:unordered
- [=Project=] - the [url ./projects.html project] this card is stored in

  [image ./img/project-create-card.png]

- [=Issue type=] - the basic purpose of an issue (Improvement, Bug, ...)

  [image ./img/issue-types.png]

  :bulleted
  - [image ./img/story-type.png Story] - functionality or feature expressed as a goal, something like "As a user, I want to be able to pay for my order via PayPal"

  - [image ./img/bug-type.png Bug] - a problem/error

  - [image ./img/epic-type.png Epic] - a collection of issues, issues are linked through 'Epic link' (see below)

  - [image ./img/task-type.png Task] - a small piece of work

  - [image ./img/sub-task-type.png Sub-task] - 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.


- [=Summary=] - a (required) brief explanation of the issue

  [image ./img/summary-create-card.png]

- [=Description=] - detailed explanation of the issue

  [image ./img/description-create-card.png]

- [=Reporter=] - person who created the issue

  [image ./img/reporter-create-card.png]

- [=Assignee=] - person who will work on the issue

  [image ./img/assignee-create-card.png]

- [=Labels=] - tags with which you can organise even more the issue

  [image ./img/label-create-card.png]

- [=Epic link=] - link of issue with type Epic

  [image ./img/epic-link-create-card.png]


## Creating

To create a card yourself, you need to [=press the [`Create`] button on the top bar=].

[image ./img/create-header.png]

## Viewing

[=All=] cards (issues) can be viewed from a [url ./projects.html project]'s side menu, under 'Issues'.

[image ./img/issues-sidebar.png]

Of course, they can also be viewed through [=[url ./filters.html filters]=] and a [=[url ./projects.html project]'s board=].

## How to use

By default, opening a card presents, at the top, it's [=key=] (think of it as an ID),

[image ./img/card-key.png]

it's [=summary=] below it,

[image ./img/card-summary.png]

options for adding [=attachments=], [=subtasks=], [=linking issues=] and [=adding more apps=] (think of apps like extensions),

[image ./img/card-attach-subtask.png]

following are the [=description=], [=actual attachments=], [=subtasks=], [=linked issues=], etc.,

[image ./img/desc-att-sub-link.png]

and at the bottom you have the [=activity=], consisting of [=comments=] on the issue,

[image ./img/activity-comments.png]

[=history=] of things that have happened to that issue,

[image ./img/activity-history.png]

and [=work logs=] (a bit later we talk about them in more detail).

[image ./img/activity-work-log.png]

### Right side

To the right side, you have all of the different [=properties=] (some fields without a value will be hidden).

[image ./img/card-right-side.png]

On the top right you can change [=watch options=] ([url https://www.idalko.com/jira-watch-issues/ watching an issue] means you get notified by all changes done to it), you can [=share=] the card and do [=actions=] (the three dots).

[image ./img/card-top-right.png]

[=Actions=] are things you can do to the whole card, like moving or deleting it.

[image ./img/card-actions.png]

The most notable options are [`[url https://confluence.atlassian.com/jirasoftwarecloud/logging-work-on-issues-902499028.html Log work]`] and [`Add flag`].

### Work log

In Jira, you can [=estimate how long an issue will take for it to be resolved=]. This is done through [=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.

[image ./img/time-tracking.png]

The time remaining takes a [=default=] value from the [=previous time log=], so you don't need to specify it every time.

### Issue flagging

A [=flagged issue=] is an issue that is very important. Flagged issues are displayed in yellow to signify their needed attention.

[image ./img/flagged-card.png]

### Basic issue information

On the bottom right you can see [=when the issue was created=] and [=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 https://confluence.atlassian.com/adminjiracloud/changing-a-field-configuration-844500798.html here].

[image ./img/time-and-configure.png]