Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Best setup for one team, multiple projects both small and large

Nicole Paul
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Apr 20, 2023

Hello! I'm new to Jira and trying to find the best solution for setup for my team.

I work with a small team, but we receive multiple projects. These projects can range anywhere from a few weeks to a few months and sometimes longer.  The projects can be as small as making a report or as large as predictive analytics.

Does it make sense to create multiple projects for each individual project? I want to kind of 'group' all these multiple projects under our team, but so each project can have it's own space, but still be part of the group? If that makes sense. And each project would follow the same guidelines from start to finish.

The rest of the company also uses Jira, so I want a way to group our team's projects without making 20+ 'project' boards for these multiple projects and spamming our company's projects page even for the smallest project.

Any suggestions would be appreciated! And sorry if I am using the Jira lingo wrong. :)

1 answer

1 vote
Clark Everson
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Apr 20, 2023

Hi @Nicole Paul 

Welcome to the community!

can you share more about what you are looking for especially on the reporting side 


the reason being is either approach can work it’s what’s nice about jira. But it honestly depends on a few factors:

first and foremost what type of reporting are you looking for not necessarily now but once the project is really rolling

who are involved and how do you plan on incorporating 

how do you think this will scale 


the reason for these is because one project with many boards can work very well as it’s easy to manage permissions 


but let’s say you’re part of a enterprise and longer term you know you need to make easily digestible reports to scale later separating out work by project level and higher level work can help or via different teams can help


boards are actually fairly confusing, while boards live in projects boards aren’t actually a function of one project they are part of filters so one board could have many projects in it. 

but there really is no correct answer to this however with more information there could be a better answer for your team specifically depending on longer term objectives




Nicole Paul
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Apr 24, 2023

Thanks for the response, Clark.

I guess my biggest concern is not having multiple boards, because one would be just fine across multiple projects. My concern is creating multiple 'projects' even though some of those projects are quite small (may only span for 3-4 weeks) so would it really be necessary to create it's own 'project' for it?

Meanwhile, we have 2-3 projects now that have a timeframe of months, so those make sense to have their own 'project'. But also, since we work on multiple projects throughout the year (about 10-15) I didn't want to clutter our Jira space by adding 10-15 'projects'? Does that make sense? And does it make sense that for less intensive projects (maybe less than 3-4 months time scope) that may they should all be housed under one 'project' instead to avoid clutter?

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events