![]() The flexibility and individuality of Jira Labels is profitable for personal reporting, but also a disadvantage at the same time. It also ensures that the grouping of tasks in a project is constant within the team. Having an admin set the Component ensures consistency and ease of use for users. The question of when to use Components and when to use Labels in Jira depends in each case on your company-specific requirements and way of working.Ĭomponents are best used for grouping within projects, while Labels can be used globally. When do I use Labels, when Components in Jira? Since there is no separate administration screen for labels, a large number of keywords deteriorates the clarity. Individual ability to create structure, independent of adminsĮxtended filtering options through customized termsįlexible and informal classification of Jira issuesīe aware that Labels are case sensitive and there can be Labels named “login” as well as “Login”.ĭon’t use bad abbreviations that only you know the meaning of and other people may only be able to guess.ĭo not create too many Labels. 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
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |