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
4,300,187
Community Members
 
Community Events
165
Community Groups

When to create a new project in Jira?

Edited

Hi all.

We develop and maintain a software and use Jira for task and project managment.

We develop major releases and have ongoing maintenance (bug-fixing, patches, small CRs). There are separate teams for maintenance and development. Major releases are considered a project in terms of a defined start, end, budget and scope/features and therefore have their own project managment of time and budget. In contrast, maintenance is ongoing, has no start, no end and no fixed scope.

The scope of a major release can vary dramatically and so can the development team. There might be even no development team at all and no dedicated budget sometimes and the maintenance team can handle small scopes of major releases.

Now my question:

In the past we created a new Jira project for every major-release project and we have a dedicated Jira project for maintenance.

I have the feeling that keeping it all together in one Jira project would have advantages.

What pros and cons do you see? What would be the recommended best practice?

1 answer

1 accepted

2 votes
Answer accepted
Alex Koxaras Community Leader May 31, 2022

Hi @schapsl 

I would be in favor of "one project to rule them all", if and only if all project share common ground. E.g. if you are developing websites, then I see no reason of having each website to its own project. If you develop e.g. mobile apps, and you develop them cross platform, and again share most of the settings (components, platform, workflows etc), then again I would use only one project. Of course I would try to keep my kanban as clean as possible, releasing the versions when possible, and chasing all the devs to log time and transition their issues properly.

The above setup would be very handy for the devs, since they would know that their work is only in one place.

If you have separate projects, you have to make sure that they use the same settings. This would reduce your maintenance. This may not be possible for projects that require special attention, have their own workflows etc. For very large projects (year+) most likely I would go with different projects and a dashboard to monitor their progress.

Hope that any of the above helps you!
Alex

Hey @Alex Koxaras , thanks for your input. Very much appreciated.

L

Like Alex Koxaras likes this
Alex Koxaras Community Leader May 31, 2022

Glad to know that this helped you.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
TAGS
Community showcase
Published in Jira Software

An update on Jira Software customer feedback – June 2022

Hello Atlassian Community! Feedback from customers like you has helped us shape and improve Jira Software. As Head of Product, Jira Software, I wanted to take this opportunity to share an update on...

77 views 1 3
Read article

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you