Best practice of using components in jira projects

[Marcus Lui]

We are using Jira heavily in our day to day development. I'd like to see if there are any best practices in creating project components in Jira?

For example, in your opinion, is it better to create a component for each development module in Jira or maybe finer-grained components are preferred by your team?

[Laurie Sciutti]

Hi @Marcus Lui and welcome!  I'm not aware of a documented "best practice" but components typically represent smaller chunks of your project as a whole, to make it easier to filter and assign work. 

From a development-tracking perspective, using Components such as API, Database, UI and Security (among others) is generally how teams want to categorize work related to an app.  But this can be very subjective - what works for one team may not be the best approach for another.  

Components for my project morphed over time but are pretty standard now.  I use my Jira project for managing all work related to Jira so I use these as some of my components:  Automation, BAU, Configuration, Customization, Housekeeping, Integrations, Permissions, Reporting, etc.) and it has worked very well for my team.

I would recommend taking a look at the issues in your project and start to group them into what would make the most sense from a reporting perspective and what would give you the most value. 

[Marcus Lui]

@Laurie Sciutti Thank you so much for the valuable answer. i really appricaite it Cracksnoon