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?
Components are like little sub-projects. Projects seem to be most useful when they group people together. I recommend to my clients that JIRA projects reflect the social organization to some degree, at least until the number of projects becomes very large.
Also, avoid the use of a component named "Misc" or "Other". They tend to become waste dumps of issues that no-one cares about.
I would match up the components with your modules/artifacts/jars, so each issue can be owned by a particular module (though it might have dependencies/relationships with others as well).
If you can make a strong case to have finer grained issue management than the module level, consider why you wouldn't also separate the associated module.
Having this 1-1 mapping helps clarify your release schedule, you can easily what issues version X of your project has, and which modules to focus the effort upon. It also helps simplify associations between Jira, the build system, and the SCM, e.g. if you're using Bamboo you'll likely have a build project per module, so you can simply add the association.
Create a component for each major module, or maybe even system tier (eg Backend, Frontend). I wouldn't go below-module-level granularity. You may add components for supporting activities, such as BA, Testing (agreeing with mdoar)... Components are orthogonal to versions/releases
