Explore topic-wise InterviewSolutions in .

• First take backup of JIRA Server
• Take an export of JIRA server
• Login to JIRA Cloud
• Go to RESTORE system
• Step by step IMPORT users, data and logos
• Provide PERMISSION through CONFIGURATION file
• Go live

YES

YES; we can GIVE them UNIQUE NAMES ALSO.

YES; daily, weekly, MONTHLY, YEARLY all are POSSIBLE.

YES

YES

“!”

If it is configured and allowed by management then YES. BASICALLY, it is nothing but a TASK. And tasks are allowed in JIRA.

The PERSON who is REPORTING the ISSUE.

The move issue wizard enables you to specify another PROJECT in your JIRA instance. Move wizard permit you to change certain ATTRIBUTES of an issue like

• Issue Type: If your issue is a custom 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

The basic search is better than QUICK search. But lesser than advanced search. It provides a user-friendly interface that allows you to DEFINE complex queries, without NEEDING JQL.

The quick search is the FASTEST way to define search CRITERIA. It is not so accurate. If you want to do basic search then you should use it ELSE do not use it. For example: if you KNOW which PROJECT, which keyword then use it. Do not use for complex criteria.

To use the quick search: Enter your search criteria in the search box in the header and press Enter. 

JQL STANDS for JIRA Query language is an ADVANCED explicit way to search ISSUES within JIRA. It consists of field, operator, value and keyword.

For this FUNCTION to work, one must have ‘Schedule ISSUE permission’ by JIRA Administrator.

Label for an issue is shown under details section. Using labels we can GENERATE reports for categorization, prioritization, RESOURCE ALLOCATION. We can also USE labels to keep track of things or for analysis PURPOSES.

No

No

To TRACK the progress in Agile, a Burndown Chart shows the actual and estimated AMOUNT of work to be done in the SPRINT. A typical burndown chart will look somewhat like this, where the red line indicates the actual task REMAINING while the blue line indicates ideal task remaining during the scrum cycle

In JIRA Agile, an EPIC is simply an issue type. The epic captures a large body of work. It is a large user STORY which can be broken down into a number of small stories. To complete an epic, it MAY take SEVERAL sprints. You can either create a new epic in agile or either use the issue you have created in normal JIRA board. Likewise, you can also create a story for agile scrum.

SCRUM and KANBAN

AGILE believes in delivering value to the customer on iterative basis with continuous feedback LOOP. JIRA helps in achieving that goal by streamlining the workflow into ToDo -> InProgress -> Done.

To create ISSUES in Agile, go to main MENU under Agile tab, click on "Getting Started", when you click on it, it will ask to create new board for the issues for Scrum or Kanban

YES

TWO ways are there:

• Create sub task under parent issue
• Create issue into sub task

To create sub-task in JIRA:

• Select an issue in which you want to ASSIGN the sub-task.
• Under the issue window, click on Assign more option
• Then click on create sub-task. You can also select convert to sub-task under same tab to convert the parent issue into a sub-task.
• Once you click on Create Sub-Task, a window will pop up to add sub-task issue.
• Fill up the details about the sub-task and click on Create
• It will create a sub-task under parent issues
• If you would like to add more sub-task, you can click on the plus (+) sign on the corner of the sub-task panel.
• Likewise, if you want to note down the time SPENT on the present task, click on (+) plus sign in the corner of the time tracking and put down the details in the LOG sheet.

Subtask issues are useful for splitting up a parent issue into smaller and MANAGEABLE tasks that can be ASSIGNED and TRACKED separately. This allows for better management and TRACKING

YES, XML, WORD and PRINTABLE

JIRA ALLOWS you to watch a particular ISSUE, so whenever any UPDATE comes in that issues, you will be notified. To enable this, you should:

• Click on the word "watch" in the issue window

• If you WANT to SEE who is watching your issues, you have to click on the number in brackets.

System events are generated by JIRA and custom events are generated by USER CUSTOMIZATIONS.

SYSTEM EVENT and CUSTOM event

• AUDIT LOG;

• Issue Linking;

• MAIL;

• Events;

• Watch LIST;

• Issue Collectors;

• Development Tools

DIFFERENT STATUSES are:

• To do, InProgress, Open, Closed, REOPENED, and Resolved. 

Different resolutions are:

• FIXED, won’t fix, Duplicate, Incomplete, Cannot reproduce, Done 

Different PRIORITIES are:

• Critical, major, minor, blocker and Trivial.

Following STEPS are done to create user stories in JIRA for Agile:

• Issue type -EPIC and Issue type – STORY linked to it.
• ‘Create Issue’
• Go to “CONFIGURE Fields” 
• 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.

Under Audit LOG, you can see all the details about the issue CREATED, and the changes MADE in the issues.

The Validators in JIRA CHECKS that any INPUT made to the TRANSITION is valid before the transition is performed. If a validator fails, the issue will not progress to the DESTINATION STATUS of the transition.

No. But you can use “On HOLD” feature to move back to previous state.

The steps are as follows:

• In workflow, Create a global transition to the ‘On Hold’ status
• 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, just 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.

• The name of the active workflow cannot be edited. Only the description can be edited
• We cannot DELETE a workflow STEP
• The status of the step cannot be edited if the workflow is active
• We cannot add NEW outgoing transitions if it did not had any outgoing transitions originally
• Step ID cannot be changed

If you MAKE it inactive then you can do all this.

• JIRA Considers a status as a global object. So, if you change status on one WORKFLOW then it will impact all workflows USING that status.
• If you hover over a status or transition, then you can SEE all details
• Transitions cannot be cloned in workflow designer
• You cannot directly set annotations
• You cannot MODIFY issue.editable field directly.

The BACKUP DATA INCLUDES,

• ATTACHMENTS if selected

• Users and their GROUP settings

• Avatars

• Issues

If you have configured JIRA Cloud then you can take backup. 1 backup file is ALLOWED at a TIME. Else it is overwritten.

Schemes ALLOW configuration in JIRA PROJECT. There are 7 types of schemes available but major ONES are:

• Notification Schemes
• Permission SCHEME
• Issue TYPE Scheme

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

Colors are used to SIGNIFY the effort put in the issue:

• Original Estimate is SHOWN by Blue COLOR 

• Remaining time is shown by ORANGE color

• Actual time spent is shown as Green color

Issue change HISTORY INCLUDES:

• DELETION of a comment
• Deletion of a worklog
• Creation or deletion of an issue link
• Attachment of a file
• Changes to an issue FIELD

To DISABLE mail notification for a particular Bulk OPERATIONS, you have to de-select the “SendNotification” CHECKBOX in the bulk OPERATION WIZARD.

There is a BULK Change option in the TOOLS menu on the navigator. Following kind of bulk operations can be PERFORMED on JIRA:

• Workflow Transition
• Delete
• Move
• Edit

Using the SHARE OPTION, we can EMAIL an issue to other users in JIRA. Another way to share an issue with other users is by mentioning their name in description or comments section of JIRA UI.

Security SETTINGS HELP control who should have read or WRITE access to issues. This can be DONE while creating issues or through admin.

If your source has custom types or values such as Issue type, issue status or any other custom field that does not OCCUR in target then EITHER you must CHOOSE a new issue type/status to be MAPPED or PROVIDE new values.

• TIME tracking

• Issue history

• Comments

Cloning as issue MEANS you can create a duplicate copy of the ORIGINAL in the system so that many employees can work on that single issue within the project if it is required. The cloned issue can be LINKED to the original issue. A cloned issue HOLDS following the information: 

• Summary
• Description
• Assignee
• Environment
• Priority
• Issue Type
• Security
• Reporter
• Components, etc.