Task-3

HU22CSEN0100936
ADITLA KARTHIK

What is JIRA?
- Project Management Tool: JIRA is a sophisticated software designed by
Atlassian that developers can use for project management activities,
monitoring issues and managing business operations.

- Agile Support: It is very common in Agile practices particularly in Scrum,

Kanban, and other flexible processes.
-
- Customizable Workflows: There are instances when JIRA lets teams build
workflows that correspond with the specific needs of the project.
-
- Collaboration Features: Users can participate in the editing of tasks, make
contributions, and monitor changes as they happen.
-
- Integration Capability: JIRA works well with tools like Confluence and
Bitbucket among other apps for productivity and development processes.

What is JIRA Used For?

• Requirements and Test Case Management
• Agile Methodology
• Project Management
• Software Development
• Product Management
• Task Management
• Bug Tracking

JIRA Issue is a task or a unit of work tracked in the JIRA project management
tool. An issue in a JIRA system is a distinct work item or a problem needing to be
solved, which falls under various categories based on its type or objective. For
instance:o O

- Bug: This is a problem that needs a resolution.

- Task: This is a work item or a follow up item.

- Story: This is a feature required to be developed.

- Epic: A big chunk of work that can be divided into several tasks or stories.

- Sub-task: is a controlled amount of the issue which a parent’s concern tackles.

Each Issue has some data like:

1. Summary: The issue in a few words.

2. Description: The subject provides so much detail regarding the specific issue
or the problem.
3. Priority: The need for that issue.

4. Status: The position currently is in the issue e.g. Open, In Progress, Resolve
JIRA Components
- A project is divided into sub sections.
- They help split concerns further down into sub-entities such as:
- Features
- Teams
- Modules
- Sub-Projects
- Components can:
- Produce some reports
- Calculate metrics
- Visualize them on dashboards

JIRA Issue Attributes

- Statuses: indicates the phase of the problem towards resolution [(To Do, In
Progress, Open, Closed)]
- Resolutions: describes the decisions towards the case [(Fixed, Won’t Fix,
Duplicate)]
- Priorities: displays the significance of the concern [(Critical, Major, Minor)]

Issue Security Schemes

- Limitations imposed on which users are can view issued documents
- Contains security levels and has users or their groups assigned to them.
- Can impose security levels on the issues at the time of creation and editing.
Default Permission Scheme
- Automatically attach themselves to projects that are new in the system
- Permits the creation of a permissions set in relation to any project.

System Administration
- Audit Log: review records of all the problems raised and the subsequent
modifications.
- Issue Linking: Connect issue with any other once raised already.
- Mail System: Publish issues in specific accounts using either POP, IMAP or any
other external site services.

Events
- System Events: recognized ahead by the system, for instance JIRA.
- Custom Events: Event which have been defined by users.

How to Create an Issue in JIRA Search jira in search

section
This is the interface of JIRA

Step 1: Launch JIRA software and enter your login information.

- Navigate to JIRA’s home menu.

- rom the “Project”, choose any of the following options:
- Issue Tracking Skilled Levels
- Management of Projects
- Kanban Agile

Step 2: Fill out Issue Content

- Now click on “Simple Issue Tracking”.

- Provide insight into the issue and give them a person responsible for the task.

Step 3: Create and Track an Issue

- Go ahead and click on the “Submit” button to make the issue.

- A window stating such will pop up to signal that the issue has been created.
- In this window you can take care of the following:
- Progress of the issue (Resolved and others).
- Comments and what has been assigned to who.

Step 4: Access “Issues” menu to:

- Search for relevant issues.

- Modify the details of the issues.
- Include the option to transfer issues to a word or an XML document.

Concerned splitting of larger projects:

•Splitting of larger projects into child issues for proper tracking.

•Creating any other subtasks under other subtasks is prohibited.
•It is unable to convert a parent issue into a sub-task.

Adding Sub-tasks:

•Click on one issue and opt “Assign More Options” -> Create Sub-Task.
•Provide the sub-task particulars and hit Create.
•The sub-task created can be seen under the parent created.

What sub-task could be, in case of jira?

•It can be defined as, the smaller piece of work that exists as a constituent of a
whole which is its parent issue, such as a Task, a Story and sometimes even a
Bug.
•In other ways, the main reason of having sub tasks is, to divide a complicated
action or job that is hard and needs to be completed into a number of easier
jobs that could be performed in order to accomplish the larger parent task.
•As the name suggests the sub-task is dependent on a parent issue which it is
related to, but can be viewed without a parent, with the parent issue being
more important.
•They can have their own status, own assignee, own due date, own priority.
•They come in handy when big tasks or stories need to be completed but can
be broken down into subtasks that would be easier to complete.

Workflow Chart:
• Depicts the movement or changes that have occurred in the status of issues
or problems.
• Illustrates the status of the work currently done.
• It gives a visual illustration of the sequence in which tasks are completed
• Lets the admins modify the respective workflows.
• Enhances communication among members of the group.

What are Jira Reports?

• Definition: Reports are used to present information such as the current state
of an issue, time spent on it, amount of sprint achieved, team’s velocity, and
the total workload.

• Purpose: To provide various inputs towards evaluating how well the team is
performing, the amount of sprint achieved and the state of the project overall.

• Burndown Chart: Compares how much work has been completed with the
amount of work that was estimated would be completed in a sprint. The red
line displays how many tasks remain to be accomplished, blue depicts the
target number of tasks.
• Other reporting options:

• Sprint Report
• Epic Report
• Velocity Chart
• Contol Chart
• Cumulative Flow Diagram

• Example: Pie Chart to visualize issue priorities or severities. Pie Charts can
be used to display categorical data such as:

• Assignee
• Components
• Issue Type
• Resolution
• Status

Plug-ins in JIRA:
• Enhance JIRA functionality.
• Examples:
•Zendesk
•Salesforce
• GitHub
•GitBucket

JIRA's filters:

Advanced issues can furthermore be filtered using custom filters based on

following attributes:

o Date
o Component
o Priority
o Resolution