Choose between project and component

[Tom Wong]

For my circumstances, we have a bulky project with many functions which can be dependent on each other.

Should we separate them as project per functions, or just use "Component"?

Any Pro and Cons if we choose either one?

[Valerie Knapp]

Hi @Tom Wong , thanks for your question and welcome to the community!

If I have understood correctly your question, you are asking whether to create more projects, or to have one project with lots components inside to compartmentalize the work.

Typically, you would only create new projects in Jira if there is a reason to do so. So, if some of these different functions you have, for example, would need different screens, issue types to represent them, customized workflows, or processes, it would make sense to create different projects and then to have customized issue type schemes, workflow schemes and all of that.

You could have Project 1, with Project 1 Issue Types, Project 1 Workflows and Screens and then Project 2, 3, 4, 5 with their own Issue Type schemes, workflows and so on.

If, instead, all of these work items are the same issue types, the team that is working in the project should have the same access to all of the issues and it is more the case that you want to start introducing reporting, for example, of how much time was spent working torwards the delivery of a function / component, you can use the component to package or group work items. You can also take advantage of the default assignee for components, if you want someone in project team to always be set as the assignee for an issue with that component.

It depends on your situation. If you want, you can write some more here about what you are trying to achieve and either myself or someone else will try to help you.

Cheers

[Jack Brickey]

Hi @Tom Wong , welcome to the Community.

it is hard to say what would work best for you without more info. What I will share are the following bits of info.

• use separate projects for disparate work
• use separate projects for different teams
• use separate projects for different products
• use components for different functions within the same product or area of work
• use components to help you group issues such that various metrics can be assessed and or to allow smaller groups of users differentiate their work from the larger collective