How to organize Jira for tiny team with many small projects


my team is just three people, and we do web design. We have basically two kind of projects: building new websites, and supporting (i.e. bugfixing and adding minor features) to the existing ones. We have been using to-do lists for quite a long time, but they are not flexible enough and don't capture process at all.

How would you organize this?

I could create one project for each new website that is to be developed, because there will be many stories, issues, etc.

However, I am in doubt about the websites I am maintaining. If I created one project per website, most of them would be empty, because the objective is to have most of the bugs and feature request done and closed as soon as possible. Those that are active, would usually have just one or two open issues each. Does it make sense to have one project for each of them? Or should I create a general "Support" project and open those issues there?

I do have one BitBucket repository for each project. However, one single Kanban board for all support issues whould be terrifically beneficial to organize this.

Thanks and sorry for the newbie question smile

2 answers

1 accepted

1 vote

Ney Palantir,

First thing to note, you can still have one single Kanban board even if you choose to track your issues in multiple projects. Kanban boards depend on the JQL that you setup to search for issues. 

Capturing issues in a single project or multiple projects? There are several factors you might want to consider and I have listed a few below for your consideration.

  1. Who is creating the issues? If your JIRA open to your customers and end users? If yes, determine what would be simpler for the user. Consider using JIRA Service Desk if you are using it for support.
  2. Does each of your website development and design follow a different process/workflow? If yes, you probably want to track them in different JIRA projects. Most projects might be empty, but this is not a concern.
  3. Use Components field. Components allow you to categorize issues within a JIRA project. For example, a website design project can be categorised into issues related to design, database, browser, etc. If you choose to use a single project, you can also use components to track which website you are facing the issue with.


I don't plan to give access to customers for the time being. Also, most projects do follow a similar workflow, although each one has its own peculiarities.
In the third point, are you suggesting to have one big project, with one component for each website? This solution occurred to me, but I dismissed it as a "hack" smile

Those "peculiarities" are what may require you to setup different projects.

Using components is to simply setup sub-categories within your project. How you choose to categorize, is left to you.

I also agree with @Gabrielle Bautista [ACP-JA] below. Project versions would be another consideration to add the the above list. 

Great, so I'll go with separate projects. Thanks for your quick & helpful support, it was a factor in the decision to purchase your service smile

Good luck smile

You will may also find these tutorials really helpful for your team (beta free till May).

JIRA for Software Teams

Git the Atlassian Way

Hello Bushan.

Picking up on something you said above that might be of use in my business...

"First thing to note, you can still have one single Kanban board even if you choose to track your issues in multiple projects. Kanban boards depend on the JQL that you setup to search for issues."

I am a Jira Core newbie also. How do I create one Kanban board to see issues across all my projects? Many thanks in advance!

Hey Nicholas,

Kanban boards can be based on JQLs. Setup a search across all the projects you would like to include, save it as a filter and set the permissions to public access.

Then go to your Kanban board configuration and select the filter as your issue source.

Refer to the docs at

Hope that helps.



Thanks for the reply Bushan.

What are JQLs, how do I access them and do I need any specialist knowledge to be able to use them properly?

All the best, Nick.

Have a look at the link Bhushan gave in his last comment.  JQL is a language for doing advanced queries (filters) in Jira.  You don't need specialist knowledge, Jira's advanced search does quite a lot of hand-holding, pre-filling and auto-suggesting things for you.

I will have to do it one project per website with the relevant issue types ("Development", "Tasks", and "Support Request'). I don't see a problem with empty projects, or just don't create them yet if it does not have any issues on it. One advantage I can think of this is you can take advantage of per website "Versions" (components does not have versions). 

Thank you. I will do it this way.

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,345 views 14 20
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot