In JIRA, labels describe issues, providing some brief information about them. JIRA labels serve mostly to help users to describe, navigate, track and search over issues. Labeling is a basic field, available for users after JIRA installation, any additional add-ons or gadgets are not required to turn on this option.
Labels in Jira are tags or keywords that you can add to issues to show whether they possess certain characteristics. They let you classify issues more flexibly and more informally than by assigning version numbers or components. In this article, we’ll explore how to use them in your projects.
What is label an issue in Jira?
A Label is used to categorize an issue. It is similar to the hashtag (#) used in twitter, Facebook or other social sites. It also helps while searching an issue.
The next thing we asked ourselves was, how do I rename a label in Jira?
We If you start out searching with the text ‘New’ you’ll see Jira shows us all the similar labels.. From here we can select just the label ‘New-York’ and modify this lable to rename it ‘New, and york’. Then we’re keeping everything consistent….
The next thing we asked ourselves was how do I add spacing to labels in Jira?
If similar labels already exist Jira will prompt you with suggestions. This helps keep your labels consistent. You can’t add spaced in Labels. So either use ‘-‘ symbols or use camel case with no spaces (e. g. “New. York”). Now the important point to grasp here is that any user can assign ANY label he or she likes to an issue.
What are labels and how do I use them?
Labels, as the name implies, can be thought of as a tag or keywords. They add flexibility by allowing you to align issues that are not under the same Epic or Story. Anyone can add labels to an issue, as long as the label field is available in the issue. They can be selected from a predictive list if one or more is already in use.
While writing we ran into the question “What are the benefits of adding labels to an issue?”.
They add flexibility by allowing you to align issues that are not under the same Epic or Story. Anyone can add labels to an issue, as long as the label field is available in the issue. They can be selected from a predictive list if one or more is already in use.
While viewing an issue, the label appears in the detail section of the issue. The following screenshot shows where the labels are present in the issue detail page. Once the user clicks on the label i., and e. WFT, it will display the list of issues having the same label.
What are the default fields in a JIRA project?
Our team in setting up a jira project for the first time and when creating user story there are 2 default fields, “label” and “component”. We are wonder what is intent of these fields and what should be keep in mind when deciding how to use them.