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,554,391
Community Members
 
Community Events
184
Community Groups

Insight for Jira cloud Schema ideas

Hi,

Just wondering how people have setup the schema when it come to End Users/HR.

I've made a start by having an 'End User' schema and 'Organisation' as the top level object. From there we split out into the different business groups. Each one has an 'Employee' object type and then under that we have 'Office', 'Departments' and under that we have 'Teams' We also have 'Role' under 'Employees' 

I'm wondering if we could just have 'Offices' object type under 'Organisation' and reference this in all groups. Also should we have an object type for 'Roles' or would that be better as a selective attribute?

Would like to take a look at some templates but cloud version doesn't allow them yet.   

 

0 comments

Comment

Log in or Sign up to comment
TAGS
AUG Leaders

Atlassian Community Events