JIRA is a project management and issue tracking tool used by agile teams. It allows users to prioritize, assign, track, and audit issues like software bugs, tasks, and change requests. Originally an issue tracker, JIRA now provides customizable workflows for tasks like requirements management and support ticketing. It is used by many large companies and offers plugins to extend its functionality.

1. JIRA SOFTWARE
BY: ATLASSIAN SOLUTIONS

2. ABDULLAH SHAHNEEL FA16-BSE-006
RAMEEZ FA16-BSE-010
WAJIHA OBAID FA16-BSE-048

3. JIRA
 JIRA is derived from Gojira (the name for Godzilla in Japanese) which was
referenced by Atlassian Sol. to Bugzilla (a bug tracker and testing tool of
Mozilla).

4. What is JIRA?
 JIRA is a #1 development and tracking tool used by Agile Teams all around the
world
 JIRA lets you prioritize, assign, track, report and audit your ‘issues’, from software
bugs and helpdesk tickets to project tasks and change requests
 More than just an issue tracker, JIRA is an extensible platform that let’s you
customize to match your business processes
 JIRA improves quality by ensuring all tasks are recorded down with all the details
and followed up till completion
 JIRA lets you organize sprint meetings between your team related to one or more
issues.

5. A bit of history
 Back in 2002, Atlassian launched an issue tracking tool (JIRA) in competition to Bugzilla which
was developed by Team Mozilla for tracking bugs.
 At first JIRA was purely an issue tracker
 But later it was split into 3 packages
 JIRA Core – Business Solutions, HR Solutions and Generic kind of project management
 JIRA Software – base software including agile project management, an Issue and project tracking tool
 JIRA Service Desk – Customer’s service care center

6. One application. Many uses.
 Bugs/Change Requests Tracking
 Help-desk / Support / Customer Service
 Project Management
 Meeting schedular
 Task Tracking
 Requirements Management
 Workflow / Process Management

7. Jira
workflow

8. companies which use Atlassian’s
JIRA Software:
 NASA
 Twitter
 LinkedIn
 eBay
 Cisco
 Sony
 Uber
 Tinder
 And many other…

9. How it works?
 Jira dashboard
 contains many useful functions and features to handle the issues easily.
 Issue tracking & management
 defines workflow of project management
 Product Management
 allows creating the project and inside the project, creating sprints

10. JIRA DASHBOARD

11. How it works?
 Configurable dashboard with widgets
 provides a dashboard with widgets to track project tasks, user workflows, etc.
 Reporting
 provides reports to understand the progress of the project
 Scrum & Kanban
 used for managing your board and to manage bugs, epics in the system
 Plug-ins Support
 provides tons of external plug-ins to manage your product.

12. Reason to use JIRA
 Provides you good and easy to understand web-based GUI.
 Provides you good team and project management.
 Provides you effective search options and query language to search for issues
and reporting.
 Lets you edit issues, move the issues between projects and issues can be
exported to pdf or excel.
 Provides you plug-ins for your different requirements.
 It can be hosted easily on sever and provides good support from Atlassian.

13. What is JIRA Issue?
 ISSUES are the heart of JIRA
 JIRA issue would track bug or issue that underlies the project.
 Once you have imported project or created project then you can create issues.

14. ISSUES SCREEN (according to project)

15. ISSUES TYPES
 They can be:
 Sub task
 Technical task
 Bug
 Epic
 Improvements
 New feature
 Requirements
 Story
 Task

16. ISSUE TYPES

17. JIRA Components
 Components are sub-sections of a project; they are used to group issues within
a project into smaller parts.
 can generate reports, collect statistics, and display it on dashboards and so on.

18. BOARD of a project to track changes

19. GENERATING REPORTS

20. JIRA screen
 Where issues are arranges and represented in field
 Can assign screen type for each issue
 click on Issues then click on Screen Schemes and then click on "Associate an
issue operation with a screen"

21. ROADMAP of a project to see work progress in the form of epics

22. Issue Attributes
 Issue Attributes encompasses
 Statuses:
 To do, In Progress, Open, Closed, Reopened, and Resolved
 Resolutions:
 Fixed, Won't fix, Duplicate, Incomplete, Cannot reproduce, Done
 Priorities:
 critical, major, minor, medium, blocker and Trivial.

23. CREATING A NEW ISSUE (epic, story, task or bug)

24. Cont…

25. SPECIYING RESOLUTION TYPE

26. SCREEN TO SEE ISSUE DETAILS

27. JIRA vs BUGZILLA
The basis of comparison JIRA BUGZILLA
DEFINITION Jira is an exclusive issue
product developed by Atlassian
Bugzilla is a Web-based
general-purpose bug tracker
also a testing tool formerly
developed and used by the
Mozilla project
License Commercial Free
Server-Side Architecture J2EE, Tomcat, Lucene, MySQL,
Oracle, PostgreSQL
MySQL, Oracle, PostgreSQL,
Server load Considerable Low
Access Control JIRA has a further manageable
permissions model, more
conventional and arguably
convenient. Migrating from
Bugzilla security groups might
be not a simple task.
Security groups: quite flexible,
however a bit mind-bending
characteristic for grouping
& issues plus granting
permissions.

28. Conclusion – JIRA vs Bugzilla
Bugzilla gives flexible although complicated features for grouping issues,
users and for allowing permissions
whereas
JIRA has a simple model about the permissions, so it is extra traditional and
relevant, it is a challenging task to migrate from Bugzilla security groups.
So, JIRA and Bugzilla are pretty much different although, they have some
common characteristics nowadays JIRA is most commonly used in software
companies.