new company managed project

[sharos.pillai]

Hi there, 

I am creating a new company managed project.

Should new request types, issue types and custom fields be created or should we be using previous standard and custom field?

I am trying to understand the usual process that Jira Administrators follow.

Thanks

SP

[Nic Brough -Adaptavist-]

Welcome to the Atlassian Community!

I am sorry that the answer you got before was misleading - it was generated by an AI that has no understanding of your question or Atlassian software.

It is both - you should reuse where possible, but not be afraid to create new things if the project needs it.

Company-managed projects mostly use schemes for their configurations, like screen, workflow, notifications etc.  Schemes are global objects defined by your admins, and can be used by many projects.  

The usual pattern is to have sets of standard schemes which the projects then share, but when a project has a good reason to diverge from the standards, then create new schemes (possibly for only that one project) as needed.

As an example, one of my old customers had a set of schemes for 

• Teams using Scrum (so we had a Scrum permission scheme, a Scrum field configuration scheme, a Scrum workflow scheme, etc)
• Teams using Kanban (so a set of schemes named Kanban)
• Teams using a more waterfall approach
• The Operations team (who used one project, but would create "initial implementation" projects for new products, but being shut down after the whole Ops team had got familiar enough with it to handle it in the main project)

Then the HR team, the technical authors team, and the Atlassian admin team (meaning me and most of the technical authors team), and other teams that needed some form of tracking or helpdesk, all had their own heavily customised schemes that were mostly not shared at all.