You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Jira component is an issue-grouping technique, used for breaking all project’s issue pull into smaller parts.
📊 Components offer a great way to structure issues in Jira; especially when you work with reporting and need to set up automation.
But as any other data-organizing technique, they require special principles and some maintenance to keep your Jira instance clean and your infrastructure well-performing.
Our team at Jexo have created this 5 Tips on How to Use Jira Components Infographic for you to save as a reference or reminder of the best practices when using Jira components. 👇👇👇
If issues are the bricks of your project , components act like the building blocks. 🏗
They are especially handy when you want to generate quality reports, collect useful data and be able to organize it for further breakdown and analysis.
Companies use Jira issues to track individual tasks of various kinds, eg. user stories, separate features to build, software bugs, or even internal tickets, like the ones HR department needs to track.
In these cases, components help to group these issues based on their functionality, features, departments, and so on.
Components are popular for a number of reasons:
In other words, components are custom fields with unique features that help you streamline your process and segment issues in your project.
A great advantage of components is that they require a Jira admin or project lead to create or edit them, this way individual users won’t be able to interfere with the project data.
However, Components can only be used for Company-managed projects at the moment and are by default project-specific, but the latter limitation can be overcome with the help of apps that allow creating cross-project components.