Check out sample Adaface MCQ questions on Jira topics
Are you a candidate? Complete list of Jira interview questions 👇
- What is a workflow?
- What can be referred to as an issue in Atlassian JIRA?
- List out the source control programs with which it integrates?
- Why use JIRA software?
- Is it possible to access JIRA cloud site via a mobile device?
- Can you disable JIRA mobile for the site?
- Explain labeling and linking issue in JIRA
- Name the types of reports generated in JIRA
- What is Cloning an Issue?
- What are the things not included in cloned issue in JIRA?
- What is the use of "Move Issue" wizard in JIRA?
- How is security setting helpful in JIRA?
- How can you share an issue with other users in JIRA?
- How you can modify multiple bulk issues?
- How you can disable mail notification for Bulk Operations?
- What does an issue change history include?
- Explain what does the three color indicates tracking times or duration for an issue?
- What are some of the popular add-ons for JIRA?
- What is Schemes in JIRA?
- What can be configured for the JIRA project and issue type?
- Is it possible to get back up your JIRA cloud data?
- What data can be backed up?
- Give some useful tips on JIRA Workflow.
- What are the limitations when editing an active workflow?
- In JIRA workflow, is it possible to transition an issue back to its previous status?
- What is the role of Validators in JIRA?
- What types of Post functions are carried out after the transition is executed?
- What is an event in JIRA?
- What is the Audit Log?
- For an Agile project, how user stories in JIRA are created?
- What is an “issue collector”?
- How you can modify multiple bulk issues?
- What is JIRA dashboard?
- Explain the step by step procedure of how an issue is created in JIRA.
- What is the purpose of the JIRA dashboard?
- Explain the Kanban board.
- Mention one similarity and one difference between JIRA Scrum and JIRA Kanban.
- What are the most useful JIRA add-ons.
- How does a service desk work in JIRA?
- How are reports generated in JIRA?
- Name some reports generated by Kanban projects in JIRA.
- Name some reports generated by Scrum projects in JIRA.
- What is the use of Move Issue wizard in JIRA?
- What are the issues types in JIRA?
- What is a Sub-task in JIRA?
- How is a sub-task created in JIRA?
- How to define a component in JIRA?
- How to delete a component in JIRA?
- What is Zephyr for Jira?
- Can we backup data in Jira Cloud?
- What kind of data can be backup?
Workflow is defined as a movement of the bug/issue through various stages during its life-cycle
- WIP ( Work In Progress)
In JIRA, an issue can be anything like a
- Software bug
- The project task
- A help-desk ticket
- The leave request form
It integrates with source control programs such as CVS, Git, Subversion, ClearCase, Visual SourceSafe, Mercurial, and Perforce.
The reason behind using JIRA is
- Upfront and fair licensing policy
- Features that is not available elsewhere
- Get the latest update on the progress of projects
- It runs anywhere and recognized with many famous companies
- Easily extensible and customizable
Yes, it is possible to access JIRA cloud site via a mobile device. You have to use the URL of the JIRA cloud site in your mobile web browser.
You can disable JIRA mobile for the site so that users can be unable to operate the desktop view of JIRA on their mobile device. JIRA mobile comes as a system add-on and can be disabled at any time.
- Labeling Issue:It enables you to categorize an issue in a more informal way than assigning it to a component or version. You can then search issues according to the label.
- LinkingIssue: This feature enables you to link an association between two issues on either on the same or different JIRA servers.
JIRA offer reports that show statistics for projects, versions, people or other fields within issues. Various reports included with JIRA are
- Average Age Report
- Pie Chart Report
- Resolution Time Report
- Recently Created Issues Report
- Resolved vs. Created Issues Report
- Single Level Group by Report
- Time Tracking Report
- User Workload Report
- Workload Pie Chart Report, etc.
Cloning as issue allows you to create a duplicate of the original issue so that many employees can work on a single issue within a single project. The clone issue can be connected to the original issue. A clone issue holds following the information
- Issue Type
- Components, etc.
- Time tracking
- Issue History
The move issue wizard enables you to specify another project in your JIRA instance. Move wizard permits you to change certain attributes of an issue like
- Issue Type:If your issue is a customs issue type and does not occur in your target project, you must choose a new issue type for your issue
- Issue Status:If you have assigned your issue as a custom issue status and it does not exist in your project, you must select a new issue status for your issue
- Custom Fields:If you have determined required custom fields for your issue, which do not occur in the target project, you must set values for them.
JIRA'S security setting restricts access to the issue to only those person who is allowed to work on the issue or a member of the chosen security level. The security level of an issue can be set either when the issue is created or when the issue is being edited.
You can email an issue by using the share option in JIRA. You can also email other JIRA users a link to the issue by sharing the issue with them or by mentioning them in an issue’s Description or Comment field.
To modify multiple bulk issues, you can use the Bulk Change option from the "Tools" menu of the navigator. All the issues on the current page can be selected for the bulk operation. The following list details the available bulk operations like
- Workflow Transition
To disable mail notification for a particular Bulk Operations, you have to de-select the “Send Notification” checkbox in the bulk operation wizard.
Issue change history includes
- Deletion of a comment
- Deletion of a work log
- Creation or removal of an issue link
- Attachment of a file
- Changes to an issue field
For any particular issue in JIRA, 3 colors like Blue, Green, and Orange is used to denote the amount of time spent on any particular issue. This information is displayed under ‘Time Tracking’ section. Each color has its own significance like;
- Blue: This color is to denote the ‘Original Estimate’ i.e. the time estimate to be invested in resolving the issue. This field has been labeled as ‘Estimated’.
- Orange: This color determines the time left for resolving the issue. This field has been labeled as ‘Remaining’.
- Green: This color defines the actual time that has been used or say spent in resolving the issue so far. This field has been labeled as ‘logged’.
Some popular add-ons for JIRA include,
- Suites utilities for JIRA
- ScriptRunner for JIRA
- Zephyr for JIRA – Test Management
- JIRA Toolkit Plugin
- Atlassian REST API Browser
- Portfolio for JIRA
- JIRA Misc Workflow Extensions
- Tempo Timesheets for JIRA
- JIRA Charting Plugin
Schemes are a major part of JIRA configuration. It is a collection of configured values that can be used by one or more JIRA project. For instance, Notification Schemes, Permission Scheme, Issue Type Scheme, and so on. There are a total of seven types of schemes.
You can configure the following things for each pair of an issue type and JIRA project.
- The order of custom fields appears on an issue screen.
- The workflow of an issue including the statuses.
- Which custom fields and system an issue can use.
- Project accessibility.
- Permissions for what a user can do with an issue.
- Versions and components available for an issue.
In JIRA, you can take a backup of your JIRA cloud data using Backup Manager. But only one backup file is stored at a time. The existing backup is overwritten by new ones.
The backup data includes,
- Attachments if selected.
- Users and their group settings.
- As such Statuses are global objects in JIRA. Changing the name of the status on one workflow will change the status on all workflows that use that status.
- Hover over status or transition to see the relevant transition labels.
- One cannot clone transitions in the workflow designer.
- In the workflow designer, one cannot create annotations.
- Directly you cannot set the issue editable property.
- If a workflow is active, you cannot edit the workflow name (only the description).
- You cannot delete the workflow steps.
- A step associated status cannot be edited.
- You cannot add any new outgoing transition if a step has no outgoing transitions (Global transitions are not considered).
- A step’s Step ID cannot be changed.
Practically, it is not possible to transition an issue back to its previous status. However, you can use the "on hold" feature to transition an issue back to its prior status. Here are the steps,
- In a workflow, Create a global transition to the ‘On Hold’ state.
- Now from ‘On Hold’ status create another transition to every other status you want to come back to
- Since the transition names cannot be the same, add a blank space at the end of it.
- Now you don’t want the status transition from the ‘On Hold’ and ‘Done’ to ‘On Hold’ So you will hide the other status “On Hold” by adding the value field condition on the global transition.
Validators check whether the input provided by the user is valid before the transition is performed.
If the validation fails, then the issue does not proceed to the destination status of the transition.
List of validators:
Required Field validators: Required field validator ensures that the field is mandatory or required. The required fields marked with the red asterisk (*) on every transition screen. In Jira, we can use the field configuration to make the fields compulsory or mandatory. With the help of Required field validators, it is possible to make the fields mandatory that makes the overall process more user-friendly.
Regular Expression Validator: Regular Expression Validator checks whether the input given to a certain field matches the regular expression that you define. It is a quite powerful validator, and its use cases vary from the simple validation, the user should provide the exact value that matches the use cases.
Regular expression: It is an expression that the input field should match.
User define message: This message appears when the validation fails.
- Validator to compare to two fields with each other.This validator is used to compare the two fields. To use this validator, both the fields must be of the same type.The following is the list of operators that this validator supports: - '>' ( greater than) - < ( less than) - >= (greater than or equal to) - <= (less than or equal to) - = (equal) - != (Not equal)
Date Compare Validator: The Date Compare Validator is used to compare the date field with the fixed date. It can support the date field types such as Date fields (Date and date with time). We can use a fixed date in the format yyyy-mm-dd hh:mm or a pattern (days, months, weeks, years).
Field Compare Validator: Field Compare Validator is a validator that compares the fields against the fixed values. It supports the following operators:
= (equal to)
!= (Not equal to)
= (greater than or equal to)
< (less than)
<= (less than or equal to)
It supports the comparison types such as String, Number, and Option ID. For example, we have a field named "Salary", and its field value should not be less than 30,000, it can be represented as: Salary>=30,000;
User in Project Role Validator: This validator ensures that the currently logged in user should be in a certain specific role. For example, only a user with a role "Developer" can do this workflow transition.
User in Group Validator: It validates that the current user should be in any of the specified groups.
User in Field Validator: This validator ensures that the current logged in user is set on a certain field. There are two options available in this validator:
You can set the status of a current user in a field.
He/she is not set in this field.
Parent Issue Type Validator: This validator is used to prevent creating the subtasks from the parent issue. We can achieve this by adding a validator to the "Create" transition from the subtask. You can also provide a custom error message for this type of validator.
Parent Issue Status Validator: This validator ensures that the parent issue should have some specific status. The status can be Reopened, In Progress, Backlog, etc.
Field Values Changed Validator: Field Values Changed Validator ensures that the user can change the value in a field.
JQL Validator: JQL (Jira Query Language) evaluates the current issue against the JQL query. In JQL Validator, the query is generated automatically related to the issue. JQL Validator provides some additional fields:
Validator message: It is used to define the custom error message if the validation fails. If you do not want to provide the custom error message, then you can leave this field as empty.
Run as user: In this field, we can define a technical user with which the JQL expression will be evaluated. If you leave this field as empty, then the current user will be considered for this transition.
Types of Post functions carried out after transition is executed includes
- Adding a comment to an issue.
- Generating change history for an issue.
- Updating an issue’s fields.
- Generating an event to trigger email notifications.
The events are classified in two a System event (JIRA defined events) and Custom event (User-defined events). An event describes the status, the default template and the notification scheme and workflow transition post function associations for the event.
Under Audit Log, you can see all the details about the issue created, and the changes made in the issues.
For an Agile project to create user stories in JIRA, follow below steps.
- Issue type -Epic and Issue type – Story linked to it. In order to do so, in the ‘Create Issue’ page, go to “Configure Fields” and select “Epic link” field to be included in the issue creation screen.
- Or you can have a product backlog by creating a main User story and having various sub-tasks under it.
An “issue collector” enables you to easily embed a JIRA feedback form into your own web site. This helps website visitors to log issues into JIRA through our website. To use JIRA feedback form, visitors to our website do not need a user account in JIRA.
You can modify multiple bulk issues by using option “Bulk Change” option.
JIRA dashboard is a dashboard which you will see when you opens up Jira.
Whenever an issue or defect is encountered while testing, it needs to be reported so that the developers can work on it and take the necessary action to fix it.
We will see step by step as how an issue is created in Atlassian JIRA.
a) Log in to your JIRA account by using valid credentials and get directed to the dashboard.
b) Click on ‘Create’ button displayed and you will be navigated to a window for creating an issue.
c) Enter all the necessary details as required to create an issue.
d) After all the details have been completed, click on the ‘Create’ button displayed on the window to create the new issue.
e) The issue id is generated which can be used in the future as a reference for tracking the progress of the issue.
The first page which is displayed whenever we get logged in to JIRA application is ‘Dashboard’ which is basically the default or system dashboard.
A personal dashboard can also be created and designed by adding different gadgets and can be edited also as and when required. These gadgets are the means to display the project progress in terms of issues, etc.
Let us understand the steps as how a personal dashboard can be created:
a) Enter valid credentials and get navigated to JIRA dashboard.
b) Click on “…” displayed on the upper right-hand side and choose option ‘Create dashboard’. You can also choose ‘Copy dashboard’ in the case of copying the currently viewed dashboard.
c) ‘Create Dashboard’ page is displayed.
d) Enter all mandatory information and click on ‘Create’ button.
e) After creating a dashboard, you get navigated to a page where there are multiple options to select and add gadgets to your dashboard.
f) There is also an option available to choose and edit the layout of your dashboard.
Any particular Dashboard can be edited, copied, shared, delete from the Manage Dashboard section.
Kanban boards are created for the projects where the team has their prime focus on visualizing the workflow and managing the project’s work in progress.
The most important feature of Kanban board is that it is found in work mode because the projects do not have their work as planned.
Let us see how the Kanban board is created in JIRA step by step.
a) Log In to the JIRA application using valid credentials and get navigated to the dashboard.
b) Click on Project dropdown and select the option ‘Create Project’.
c) Select ‘Kanban Software development’ and click on the Next button.
d) Enter all the necessary details and click on the Create button.
Similarity: Both JIRA Scrum and Kanban is considered as the most powerful process tool for optimization of work and the processes as both processes focus is on continuous optimization and visualizing the workflow. In these cases, large and the complex tasks are broken down and each individual tasks are worked on and completed efficiently.
Difference: Scrum board is the work mode where progress of sprints and tracking of its work is done. Here the team determines the list of issues that has become backlog and then these issues are moved to sprints as per team plan.
In the case of the Kanban board, the work in progress activities is being maintained and their process flow is tracked. Here the team decides the increase and decrease of the number of issues that is to be displayed in each status of the workflow.
Some of the most useful JIRA add-ons are listed below:
- Tempo Timesheets
Here is how Customers and Service desk agents work together to resolve a request in JIRA.
- Your customer submits a request to service agents through a portal or by email.
- Service desk agents see the request in their JIRA Service Desk line and investigate the issue.
- Your customer and other participants utilize the portal or email to discuss the request with service desk agent, who works in JIRA Service Desk.
- Your service agent completes the request and your customer is satisfied.
Steps to follow to generate reports in JIRA are as follows:
Step 1: Navigate to the desired board and click Reports. You can find different types of reports.
Step 2: Click Switch report to view a different report.
Step 3: Click on the switch report option to view a different report
The reports generated by any Kanban project in JIRA are
- Control chart
- Cumulative Flow diagram
The reports generated by any Scrum project in JIRA are
- Sprint Report
- Control chart
- Burn down chart
- Cumulative Flow diagram
- Epic Report
- Release Burndown
- Velocity chart
- Version Report
Move Issue wizard enables you to specify another project in your JIRA instance. The Move Issue wizard permits you to change certain attributes of the issue such as Issue Type, Issue Status, and Custom Fields.
- Issue Type: If your issue is a custom issue type that does not exist in your target project, you must choose a new issue type.
- Issue Status: If you have assigned a custom status to your issue, and it does not exist in your target project, you must select a new issue status for your issue.
- Custom Fields: If you have defined required custom fields for your issue that does not exist in your target project, you must set values for them.
Each Jira application comes with default issue types. You can use these default issue types or create your own to suit the needs of your projects and teams. Here’s an example of specific issue types within each Jira application:
Jira Core default issue types:
- Task – Task that needs to be done.
- Subtask – Smaller task within a larger piece of work.
Jira Software default issue types:
- Story – Functionality request expressed from the perspective of the user.
- Bug – Problem that impairs product or service functionality.
- Epic – Large piece of work that encompasses many issues.
Jira Service Desk default issue types:
- Incident – System outage or incident.
- Service request – General request from a user for a product or service.
- Change – Rollout of new technologies or solutions.
- Problem – Track underlying causes of incidents.
Sub-task is the way of splitting up a parent issue into a number of smaller tasks that can be assigned and tracked separately. All the sub-tasks to a parent issue are summarised on the parent issue’s main screen. Sub-tasks always belong to the same project as their parent issue.
- Navigate to the issue you would like to be the parent issue of the sub-task you are about to create.
- Select More > Create Sub-Task. You will see the Create Subtask screen.
- Fill in the details as needed, and then click Create at the bottom of the page.
Components are sub-sections of a project. They are utilized to assemble issues within a project into smaller parts. Managing a project’s components
- Sign in to JIRA as a project administrator.
- Choose Settings > Projects > and click the name of a project. The Project Summary page will appears.
- Choose Components in the left menu. The Components page is shown, demonstrating a rundown of Components and every Component’s information.
To delete a component in JIRA,
- Navigate to components screen, hover over the relevant component to display the Delete button.
- You will be prompted to connect these issues with another component if you wish.
Zephyr for JIRA is an add-on application that provides highly sophisticated test management capabilities right inside JIRA.
Yes, Jira provides backup functionality of data. But it can save backup files only once and next time when you backup, the existing data will be overwritten.
Issues, Avatars, users and their settings, and attachments that can be backup.