This is part of a blog series with our own tips on configuring your JIRA, maximizing your use of JIRA’s many features, and tailoring the platform to best suit your organization’s needs.
When using a comprehensive software platform like JIRA, it may seem difficult initially to familiarize yourself with all of its robust features. In this post, we’ve put together a list of suggested best practices on how to use the sometimes forgotten Built-in Field Values in JIRA. Using them can be a good way to filter and prioritize issues.
The Built-in Fields in JIRA can be divided into four categories: Issue Type, Statuses, Resolutions, and Priorities.
Issue Types are used to categorize issues depending on their nature. JIRA has some defaults set to help you get started: Bug, Improvement, New Feature, Task, and Custom Issue. Since needs vary, JIRA allows you to add, edit, and delete your own custom issue types.
Before you create a new Issue Type, you’ll need to decide on the names of Issue Types you need. There are a few things we recommend to keep in mind when creating a new Issue type:
First, since JIRA comes with a number of default Issue types, you may not want to create new types unless you absolutely need to. When creating a new Issue Type, be sure to use descriptive names and icons for each new Type to help you keep them organized and easily identifiable. Images for new icons can be added to the image folder. Make sure that you don’t have more Issue Types than needed for a particular project to maintain clarity and ease.
Issue Types are grouped together using an Issue Type Scheme, which is then associated to a Project. This allows you to control what Issue Types are available for each Project, and to easily maintain an overview of issues with these ascribed Types. For this reason, we recommend not using the Default Issue Type Scheme, because it includes all Issue Types in the JIRA instance.
If you plan to use Sub-Tasks, you’ll need to log in as a user with the JIRA Administrator global permission to enable them.
Each JIRA issue has a status, which indicates where the issue is currently in its lifecycle (‘workflow’). An issue starts as being ‘Open’, then generally progresses to ‘Resolved’, and then is ‘Closed’. Statuses can, however, be customized by a JIRA Administrator.
The default statuses for JIRA issues are Open, In Progress, Resolved, Closed and Reopened. However, custom statuses can also be added in JIRA.
When adding a new status, make sure you choose a descriptive name and an icon for the status you’re adding. New users might wish to add a status to indicate the very start of an issue, for example.
With JIRA, you can use Jelly Script to change an issue status automatically to a new status. This can be a neat feature, for example, when users set a time limit on the response of a customer approval for a particular issue.
Using statuses can prove useful when searching for an issue, as they can be used as a filter.
All changes to statuses on an issue are tracked, and an overview of the status transitions can be found in the transition summary in the issue.
Any issue that has the Resolution field set is treated by JIRA as "resolved". A JIRA issue can be resolved in a number of ways. The default resolution statuses are: Fixed, Duplicate, Won’t Fix, Incomplete, and Cannot Reproduce. However, new resolution statuses may be added.
The resolution status of issues is on a JIRA Global level, which means that one configuration is used for all projects.
Resolutions are added as a required field in the Resolve issue screen.
Some things to keep in mind when adding a Resolution to your JIRA:
Try to avoid having too many specific options, but rather, try to keep options as generic as possible, as they’ll apply to all Projects and Issue Types.
Make sure you select a default value that can apply to all projects, and not just the one you’re working on.
Remember that ‘Fixed’ is the default Resolution value in JIRA.
The Resolution field is often used when searching for issues or creating issue filters. For example if you want to find all open issues, you can search for issues with resolution “Unresolved” instead of having to check all possible statuses that are not “Closed” or “Resolved”.
If you’re ever in the situation where you need to open an issue that has been closed, you will need to empty the value in the Resolution field. This can be done by using the Post Function in JIRA. Post functions are configured “behind the scenes” in the workflow by a JIRA Administrator. They carry out any additional processing required after a transition is executed, which in the example above is updating an issue field. Other post functions can be:
Generating change history for an issue
Adding a comment to an issue
Generating an event to trigger email notifications
An issue’s priority indicates its relative importance. There are five default levels of priorities in JIRA: Blocker, Critical, Major, Minor, and Trivial. As with other customizable fields, your JIRA Administrator can add a new level of priority to suit your organization’s needs.
Priorities are on a JIRA Global level and therefore, only one configuration is available for all projects within each system. It is possible to not to use priority in specific Projects or Issue Types.
When adding a new priority, make sure you choose a descriptive name and an icon which suits the priority.
If you do not want all users to have permission to fill in the priority field, you can “hide” the field by configuring screen schemes and permission schemes. For example, if customers have access to create issues but not to edit issues, you can show the priority field on the edit issue screen only, but not the create issue screen. In that case, you would select one priority as a default.
Finally, it is important to avoid having too many levels of priority, as this can lead to redundancy and confusion.
JIRA’s customizable Built-in Fields offer an easy way to organize and filter projects across your organization. Make sure you keep these things in mind when managing Built-in Fields to get the best out of JIRA. Stay tuned for more JIRA best practices tips from us!