Jira¶

Introduction¶

JIRA is a tool developed by Australian Company Atlassian. It is used for bug tracking, issue tracking, and project management. The basic use of this tool is to plan, track, and release software.

At Krenovate, Jira is the most important used app due to it's project management and task tracking tools.

This manual is focussed on the Users/team members. It has been designed keeping in mind the steps to be taken by the Team members.

Account Creation¶

Your account on Jira will be created by the HR department. And you will get a link for logging into your account on your official email ID.

Jira Invite

Create your login credentials and remember the same for unnecessary hassle. Once you create your account, please contact your manager to assign you to relevant projects.

jira active

Logging In¶

To log in:

Go to -> krenovate.atlassian.net
Click on the sign in button.
Use your credentials to log in.

Tutorial ¶

Key terms to know¶

Tasks
- A Jira 'task' refers to a single work item of any type or size that is tracked from creation to completion.
- A task represents work that needs to be done.
- A task has a more technical nature.
- A task can be referred as "issue".
Few examples of tasks could be:
- a feature being developed by a software team
- a to-do item for a marketing team
- a contract that needs to be written by the legal team

task

Sub-Tasks
- Subtask issues are useful for splitting up a parent issue into a number of smaller tasks that can be assigned and tracked separately.
- It addresses issues more comprehensively and segregates the task into smaller chunks of task to do.
- A sub-task has to be totally related to the parent task.
Projects

A project is, quite simply, a collection of Tasks, that are held in common by purpose or context. Teams can use a Jira project to:
- Coordinate the development of a product
- Track a project
- Manage a help desk
Jira Software projects are flexible working spaces that allow you to group like tasks by team, business unit, product, or stream of work.

Projects don't need to be tied to the same delivery date.

projects

Workflows

Workflows represent the sequential path a task takes from creation to completion. A basic workflow might look something like this:

In this case, Open, Done, and the labels in between represent the status a task can take, while the arrows represent potential transitions from one status to another.
Epics
- An Epic is a large body of work that can be broken down into a number of smaller tasks.
- Epics group together bugs, stories, and tasks to show the progress of a larger initiative.
- An Epic can run across multiple versions.

epic

Stories
- Also called “user stories,” are short requirements or requests written from the perspective of an end user.
- At Krenovate, we do not use stories.
Versions
- Versions are points-in-time for a project.
- Versions can be termed as "Phases of launch" of a project.
- They help you schedule and organize your releases.
- You can assign tasks in your project to a specific version, and organise your sprints around completing work in that version.
- Versions that include end dates can indicate when a release is overdue.

version

Backlog
- It is simply a list of tasks that represents outstanding work in a project assigned to you.
- The Backlog gives you place to organize your sprints.
- You can create new issues or sub-tasks, organize your backlog, create versions, organize via epics, and start sprints.

backlog

Sprints
- It can be termed as a "Timeline of tasks".
- A sprint is a short, time-boxed period when a team works to complete a set amount of work.
- A sprint is a fixed time period where teams complete work from their product backlog.
- Sprints are usually one, two, or four weeks long.
Active Sprints
- An Active Sprint of a Scrum board displays the issues that your team is currently working on.
- You can create and update tasks/issues, drage and drop issues to transition them through a workflow.

activesprint

Components
- Components represent stakeholders of a project.
- Component Stakeholders are different group of people who are goig work on and use projects.
- Component is a generic term which can be used effectively to represent an module of an project.

components

Watch the tutorial to understand the key terms ¶

Task Allocation and Management¶

Tasks in Jira are allocated by your Manager. Below are a few tasks which are to be handled ONLY by managers:

Create a Project
Assign issues to Users
Manage Users/Team members
Track time for users

As a user, the most important thing to understand is the tasks allocated to you and how to manage them.

In this section, we will discusss about tasks allocated to you in detail.

Once, your Jira account is activated, your manager will assign tasks to you.

How to view your task¶

There are different ways to view your tasks:

Email:

You will receive an email intimation for task assigned.

taskmail

Click on "View Issue" - You will be taken to the task description page in Jira.

Browser:

Login to your Jira account
Go to -> Projects
Choose the project assigned to you.

choose project

Go to -> Backlog
You will see list of tasks assigned to you

issue list

Click on the issue to be worked on

choose issue

Description of Task¶

Task description will tell you all about the work to be done under that task.

taskdesc

Top Panel¶

The top panel of the description page shows options as below:

Name of the issue: It shows the name of the issue.
Attach: You can attach relevant files, images from the attachment tab below the task name.
Create Sub-task:
- Within the assigned task, you can add sub-tasks to organise your work.
- Click on Create Subtask
- Enter the description of the sub-task and click on create.

Right Side Panel¶

On the right side of the screen various options are available which are described below:

Status of the task:
- When task is assigned it shows "To Do"
- Task should never be marked as "In Progress"
Assignee: It is the name of the user to whom the task is assigned to.
Reporter: This shows your manager name
Time Tracking: This shows the duration of time spent in performing the task.

Note: Time is tracked using the Hubstaff Recorder App

Sprint: Shows the name of the active sprint of which the task is a part.
Priority: Here the priority can be set as low, medium, high depending on the project requirement.

Bottom Panel¶

The Bottom panel shows details of various activities occuring in the issue.

Comments: While you're working on an issue, you will probably need to share some information, clarify some requirements, or discuss some details about the issue with your team. This is easy to do with issue comments:
- You can comment, attach files, send links through the comment section of the task.
- To email other users about your comment, simply mention these users in the Comment text box (by typing @User's Name). An email will be sent to the users' email addresses that are registered with their JIRA accounts.
- All formatting options are available within.
- Click on Save
- Once you add a comment, a mail notification is received by the tagged person.
History: The history tab gives a detailed view of all the activity that takes place while performing the task.

taskhistory

Work Log: The work log tab shows the time spent of doing the task.

tasklog

Marking Task Complete¶

After your work has been reviewed and approved, the last step is to close or resolve the issue.
Select "Done" in the task status option.

task done

Help & Guides¶

Follow the below useful links for more information:

To Do List¶

Once you finish the training, follow the below task list. Finishing these tasks would mark your Jira training complete.

Ask your manager to assign a task for you.
Add a comment to the task
Attach some test files and share with manager
Mark the task complete.

Last update: August 10, 2020