Power of Jira admins - Company managed projects

The creation

       

 

Only users who have the Administer Jira global permission can create company-managed projects. Cool..so those are the infamous Jira admins.  Its not a role, its the permission. In some articles we saw org admins, site admins, jira admins, system admins. System admins is not being used as well. That was on server. Everything is on cloud, or if you want to complicate things, on DC. Company-managed projects have way more customization options. Heck, just look at the board configuration. Quick filters, card colours, card layouts, columns, swim lanes, etc. Those buzzwords, there are bunch of them. 

When creating a project, you don't have the access levels. Everything is based on the permissions here. Either you pass or you shall not pass. 

                                              

 

This picture is perfect for this occasion. Company managed projects use schemes for almost everything: issue types, screens, fields, workflows, field configuration, permissions, priorities. The list goes on. For access, the Browse projects permission is needed in order to see the project and browse the issues of that project. You can be the super admin, if you don't have this permission, you can't do much.These projects let you create multiple boards - there isn't really a limit on how much, but lets be real. You don't need more than 10. More reporting options especially for Epics and Versions. Applying issue security. Defining which fields are mandatory and which are optional.

 

The list is almost endless.