JIRA is an issue tracking product or a software tool developed by Atlassian, commonly used for bug tracking, project management and issue tracking; it is entirely based on this three aspects.
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
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 latest update on the progress of projects
It run 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 just 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 any time
Labelling 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 label.
Linking Issue: 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
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.
JIRA’S security setting restricts the access to the issue to only those person who is allowed to work on the issue or a member of the chosen security level. 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 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:
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 worklog
Creation or deletion of an issue link
Attachment of a file
Changes to an issue field
Three color will be displayed representing the amount of time spent behind the issue:
Original Estimate (Blue): The amount of time originally estimated to resolve the issue
Remaining Estimate(Orange): The remaining amount of time left to resolve the issue
Time Spen or Logged (Green): The amount of time spent so far while resolving the issue
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 total seven types of schemes.
You can configure following things for each pair of an issue type and JIRA project.
The order of custom fields appears on an issue screen.
Workflow of an issue including the statuses.
Which custom fields and system an issue can use?
Permissions for what a user can do with an issue.
Versions and components available for an issue.
In JIRA, you can take 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 a 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 “onhold” feature to transition an issue back to its previous status. Here are the steps,
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 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
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.
5th April | 08:00 AM