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
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.
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"
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.
You will may also find these tutorials really helpful for your team (beta free till May).
JIRA for Software Teams
Git the Atlassian Way
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!
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.
Hope that helps.
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).
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!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot