Team vs Company Managed Projects Demystified | Atlassian Jira | Jira Software

One of the biggest frustrations that users have with #Jira happens when they pick a #team managed project type. Using a Team-Managed project type with Jira is like buying a Ferrari, but swapping the engine out with that of a Corolla. With a Team-Managed project, you just end up handicapping your team.
If you feel that Jira just isn't working for you or your team, then chances are you simply selected the wrong project type. #Company-managed projects is what you want to have in order to unleash the full power of Jira.
I should caution that it is not trivial to convert between Team and Company managed projects today. You essentially need to start over if you realize you have a team managed project and then learn that you really need a company managed project.
Do not make the same mistake that many have done. Learn the difference between the project types in this video and pick the right one that is going to give you less frustration and allows you to scale with your team.
With that said, you do need more experience in managing Jira projects when you select a company managed project because some of the settings are more powerful that they require someone that is more comfortable tweaking the settings. But, don't let that stop you from picking the right project type. There is an amazing Atlassian community to help you with your configuration issues.
Jira Merch:
linkpop.com/apetech
Link to Atlassian's Jira products:
www.atlassian.com/software
Link to Jira Cloud Pricing:
www.atlassian.com/software/ji...
Link to my Fiverr profile:
www.fiverr.com/alexortiz924?u...
Link to my Upwork profile:
www.upwork.com/freelancers/~0...
Link to my personal website: (redesign with focus on Jira coming soon!)
www.apetech.me/

[@IvanGarcia-su6tk]

Great information, I'm learning Jira in this moment and your videos are amazing !!

[@ApetechTechTutorials]

Glad you are enjoying them. Many more are coming this Summer!

[@prasanthr4427]

Thanks for the video. very helpful!

[@ApetechTechTutorials]

Glad it was helpful!

[@jimiwikmanofficial]

Good stuff as always!

[@ApetechTechTutorials]

Thanks for the support Jimi!

[@denysdarakov8015]

Everything is great, thanks! Except for the auto captions - lots of mistakes there A quick question: can there be multiple Jira admins (with global permissions) in one company?

[@ApetechTechTutorials]

Will work on the auto captions. Might not include them going forward. . . . As for multiple Jira admins, yes you can have multiple site-admins which basically do pretty much anything in Jira. You can also have multiple ORG admins which also manage things like billing/subscriptions.

[@agarwalaanchal]

Hey, thanks a lot for your playlist on jira. We have started using Jira for our company recently and are facing a problem - when we create a project for a department, we assign issues to different users, but we want to restrict one user from seeing the issues assigned to another user. Would really appreciate your guidance on this, thanks.

[@ApetechTechTutorials]

This is possible. All you need to do is modify your permission scheme so that browse has assignee in it. BUT, I don't recommend going down this route as it defeats the purpose of Jira.

[@robertcruz7866]

Hi @apetech, My team wants to move from SCRUM to KANBAN. We are on a company-managed project, and we created our KANBAN boards (on an existing project with sprints) The problem we have is that stories can not be transitioned to different statuses because it says the story/ticket is "not assigned to a sprint" Suggestions on how to resolve?

[@ApetechTechTutorials]

Make sure your statuses (columns) in your new board match the old scrum board. IF you still have trouble, feel free to schedule a free 15 minute call with me. Link in bio!

[@robertcruz7866]

@@ApetechTechTutorials Thanks for the reply. We'll give it a try. If we're still having trouble, will likely take you up on that offer. Thank you very much in advance!

[@ApetechTechTutorials]

@@robertcruz7866 Good luck!

[@SanlaSandesh]

Hi can we restrict epic and story creation to a few users?

[@ApetechTechTutorials]

Yes and No. You can restrict issue creation . . but that restricts all the issue types. You also have the option to add conditions via your workflow right on create to restrict this to members of a specific group/role. But, that would require your epic/story to have their own (or shared with each other) workflow. A little more advanced.

[@hatemahmad1990]

Which Jira version is this?

[@ApetechTechTutorials]

Jira Cloud. Free, Standard, Premium, and Enterprise pricing follow the same concept.

[@hatemahmad1990]

@@ApetechTechTutorials I want to know if version 9 has team managed projects or we can only create company managed ones

[@ApetechTechTutorials]

@@hatemahmad1990 Team-managed projects are a Jira cloud thing only. Sorry.

[@hatemahmad1990]

Thank you!

[@lblockerwr]

Cool, but stop begging for likes so much.

[@ApetechTechTutorials]

This is such an old video. But hopefully you liked the video.

[@RinoMoen-xy6sg]

11:18