JIRA is an issue tracking product developed by Atlassian. There are three main products for manage projects and track issues;
JIRA Software (for Software development teams),
JIRA Service Desk (for IT teams and customer service),
JIRA Core (for Business teams)
If you have a development team and you want to manage your software development project (especially agile software projects), JIRA Software is for you. You can use JIRA Software to plan, track and release your software project. There are simple tasks as Create sprints(Only Scrum Masters can create and manage sprints), fix bugs and monitor build statuses.
If you are a member of an IT Team or you are working on customer service, JIRA Service Desk is for your team. You can use JIRA Service desk for dealing with problems and service requests. The basic tasks on it are Log service tickets, resolve service requests and monitor service queues. JIRA Service Desk is used for create and manage service desks.
JIRA Core is used by business teams to manage their projects. For example, managing job applicants by Human Resources would typically be managed in JIRA Core. The basic tasks on JIRA Core is creating and managing business tasks. JIRA Core is used for manage tasks in business projects.
Your job role determines what you can see and do in JIRA. What you see depends on your access, your permissions and how JIRA is set up at your side. Your job role is assigned by your JIRA Administrator. Here some examples of job roles;
-Scrum Masters (They can create and manage sprints on JIRA Software)
-IT Manager (They can create service level agreements and request types on JIRA Service Desk)
-Human Resources Managers (They can create reports on JIRA Core)
Now you know which product is appropriate your team. After your product choice, lets see how can you work on projects on JIRA;
All projects are made up of issues and workflow on JIRA. Issues and Workflow are part of all JIRA projects whether in JIRA Software, JIRA Service Desk or JIRA Core.
An issue in JIRA is a tasks. With the most simple definition, an issue is a packet of work that belongs to just one project. Issues contains informations about a particular work like summary of the issue, what type of issue it is(it may be a task, bug, story, incident, problem or change), how important it is, who created it, who is working on it and its status.
Issues are unique in JIRA. But an issue can contain a link into another issue. By linking two issues, your team members can easily navigate to the linked issue to see what is in done. Also, when the issue has done, other issue automatically be updated.
Also, you can add attachments like a screenshot into an issue. By adding an attachment into it, your team members easily access the important information about that issue.
Issues are stored in fields on the workflow. Here is a simple workflow;
To Do–> In progress –> Done
If an issue is not assigned to anyone yet, it is placed on ‘To Do’ field. If someone is working on an issue, it will placed on the ‘In progress’ field and if an issue is finished it will placed on ‘Done’ field. So, it is easy to track your project. You can see who is working on which issues and which issues have done.
To sum up;
JIRA Software -> Used by software development teams.
JIRA Service Desk -> Used by IT Teams and Customer Service
JIRA Core -> Used by Business Teams.
Your job role determines to what you see on JIRA which is assigned by your JIRA Administrator. The basic parts of JIRA projects are issues and workflow. Issues are work packages that are contain information about the work and workflow divided into simple fields and these fields shows which issue on which status and who is working on it or who has finished it.
JIRA is really make easier to manage and track works on the project. Just choose a product which is appropriate for your team and make the things more efficent.
For more information about JIRA you can visit Atlassian Documentation.