download Atlassian Jira Software Cloud Standard

Step 1: Create a new Jira issue or open an existing one. In general, labels increase flexibility in Jira by allowing the grouping of issues that were not created under the same Epic or Story. Because in this way, labels from other projects can be accidentally selected, and might have a different connotation. What looks like a pure advantage at first glance can be a disadvantage at the same time.

This means that a Label created in the development project can also be used in the marketing project. Unlike Components, Jira Labels are project-independent. It is not possible to enter spaces in the text field. However, this only works if the corresponding text field is activated in the issue. They are used to group and categorize Jira issues using keywords that each user can type into a free text field of an issue. Note that there is no hierarchy to help group the components into a better structure.Īnother way of organizing is to use Jira Labels. We recommend 15 to 20 components per Jira project. After all, an endless-looking dropdown menu would not be user-friendly. So only choose abbreviations that your team understands.ĭon’t create too many components. But if you specify DtB as admin for database, this is not particularly self-explanatory.

Simplified reporting through filtering using Jira ComponentsĪbbreviations are certainly helpful and those like UI, UX are commonly known. Avoidance of typing errors due to unique definition of Component names by adminsĬlear representation of all components on the administration page

Download Atlassian Jira Software Cloud Standard