Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

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,464,407
Community Members
 
Community Events
176
Community Groups

Company-Managed projects and schemas

I'm new to Jira Admin and have taken Jira Admin 1/2 training.  My question relates to CM projects and schemas.  I expected, in this example, that and Issue Type Schema, when assigned to a CM project, would appear the same when I viewed the Project Summary.  In the image example.  I don't understand why the additional item type called 'Feature' appears in the Project Summary, but is not part of the Schema.  Are Schema's just a 'starting-point' for CM projects?  Can the Project Administrator add more item types 'local' to their project?  Is this an expected behavior across all Schemas?  Or is there a security change I need to make to prevent this?  A bit confused...Jira Issue Type Q.png

1 answer

1 accepted

3 votes
Answer accepted

Hi @Athas Mark 

You nailed it with "schemes are just a starting point". They are indeed that. Having been around this block a few times, I do wish Atlassian had a better config for new projects that I could pick all the items I need in  new picture without having to resort to plugins.

Basically, the base scheme would be for absolute new users or those who just don't care beyond that set of items to stand up something that works. Does it fit all the cases? No. But it works.

In my world, which is a mix of Company and Team managed projects, It is exceedingly rare that I use the scheme, workflow, or... all the things provided by a generic project standup. The only time I really do is when I provision a team managed project for a group and know they will do all these things for themselves.

In my environment, I have many dozens of issue types that help me craft each company managed project exactly to a team/group/division's needs. I have ~900 custom fields. I have dozens of statuses. 

So... no security constraints. To make those both the same, you'd merely need to add Feature to one of them or remove it from the other and they would totally match and be exactly the same projects plus/minus that issue type.

Jira is enormous. It'll work out of the box with no changes but can be as complex and customized as you need it to be.

@Mike Rathwell Thank you for the quick and detailed response.  Just when I assert that I know something about Jira behavior.  I learn it does not behave that way...  It appears that Company-Managed Projects, are just Company-started projects.  I'm beginning to think that Project Administrators have all the rights and privileges of a team-managed project.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events