Where do software modules map in Jira?

[Goran]

Hi,

my company is planning to shift our support / issue tracker from vTiger to Jira, so we want to understand how our products fit into Jira setup. Since service desk is a project of its own, I would first try to figure out how to setup Jira for development.

We have a Product Suite, and in it we have approx 10 different modules (applications). Most (but not all) of those modules are just a means to use for our main module. Each our developer is capable on working on any of these modules, there is no separate responsibility.

We would also want to include a 3rd party team for helping us build some new module in the future.

How do we setup Jira? We can have one project for each module, or we can have one project for all modules.

In 1st approach, it could be difficult for developer to move from one project to another, if he is working on several. Also, I am not sure if we are loosing tracks on a suite progress (all projects progress combine), so that we can be aware if we are on track with release date.

In 2nd approach, all tasks would be part of a single project, so it could become difficult to follow. Is there a way to have each module represented separately in project (maybe as components?), so that user can look at only one component at a time? Component is something that should be long lived, until its deprecated and pulled out from usage.

All other things like initiative, theme, epic seem to have a definitive life span, and at one point, once achieved, are closed, so I do not think that our modules are a good fit for one of them.

Any advise is welcomed.

Thanks,

Goran