nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

What board type and Bussiness procces is better to use?

Max Roslov

Hello lovely Comunity!

I am kind new to Jira and all this compliacted features)

My qesution is just to find out the best approach to impliment in my projects.

To describe it in two words : its continious development , QA testing, and bug fixing.

around 10+ users

I know this coomunity have seen miriads of projects...

if some more information needed i am happy to provide it

Accepted answers

John Funk

Hi Max - Welcome to the Atlassian Community!

A lot depends on the level of customization you might need to do. I find that the Classic Software projects are best for that. But it possibly involves a little bit more to make simple changes. But you can also share many objects between projects.

Next-gen projects are very easy to setup and maintain, but there is very little you can customize and there is nothing that you can share between projects.

Business projects are fairly straight forward and are somewhat of a middle path between Classic Software and Next-gen. But again, they have very little customization that you can do.

My best advice is to create one of each and then test them out to see what they can do for your. Then try to make some possible changes to see how each reacts.

You cannot convert straight from one type to the other but you can go through a migration process, more or less, if you end up going a different route. I would just suggest that you don't get too far down one path or the other before making a decision which route is best based on your testing.

All comments

John Funk

Hi Max - Welcome to the Atlassian Community!

Next-gen projects are very easy to setup and maintain, but there is very little you can customize and there is nothing that you can share between projects.

Business projects are fairly straight forward and are somewhat of a middle path between Classic Software and Next-gen. But again, they have very little customization that you can do.

My best advice is to create one of each and then test them out to see what they can do for your. Then try to make some possible changes to see how each reacts.

Max Roslov

Hi John and Thank you for your reply , what i am thinking is a next gen project, as for now it is easy to set up and clearly easy to maintain. Also i will make copies of the other types and try to follow the guided steps to find out which suits the best.

And other thing as we heve lots of continious tasks and are swithing between them quite frequently i am thinking to impliment a Kanban board, to react fast, am i on the right track?

Thank you!

John Funk

I definitely prefer the Kanban framework and that's pretty much what we exclusively you in our organization of more than 50 teams. But we use heave customization to share schemes across those teams so Next-gen would not work for us.

And just to reiterate, this is from some of Atlassian's training:

In summary: Classic projects have a huge number of options for planning, tracking, and reporting on your team's work. They're powerful and highly configurable. Next-gen projects are fast to set up, easy to configure, and user-friendly. Only Jira administrators can create classic projects, but any user can create next-gen projects by default. Also project configuration can be shared between classic projects. Whereas any changes you make to a next-gen project won't affect other projects.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

board

jira-work-management

process