You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I though I'd share what we did at one company to try to simplify and keep schemas organized. We used Project Category along with pre-defined simple standard naming convention to organize our work. Inherently, Project Category has no super powers except making it easier to search across multiple projects of the same sort/flavor.
So firstly, we chose a descriptive name for our categories. For example, in the Customer Service part, we chose:
- Corp Customer Service Gold
- Corp Customer Service Silver
- Corp Customer Service Standard
And for internal, we have a few categories. For example:
- Corp Business Support
- Corp Cost Center Projects
- Corp Software Development
Then we decided that all schemas would have a prefix referring to the Project Category that particular schema was to be used for. As an example, if I was creating the schema for the Corp Customer Service Silver category, I would name them:
- Corp Customer Service Silver Issue Type Scheme
- Corp Customer Service Silver Workflow Scheme
- Corp Customer Service Silver Incident Workflow
- Corp Customer Service Silver Change & Release Workflow
- Corp Customer Service Silver Issue Type Screen Scheme
- Corp Customer Service Silver Field Configuration Scheme
- Corp Customer Service Silver Incident Field Configuration
This makes it a lot easier to see what Project Category my changes are going to affect. It also makes it much easier to apply the right schemas to the project, for example when a customer moves from a Silver status to a Gold status.
What this approach does also is helping the Jira admin place a new project. I.e. when a business unit asks for a new project, the Jira admin is right off the bat thinking where he/she is going to place this new project. This has also made it easier for the business units to talk "Jira jargon" with the Jira admins because they often say; "I need a project like this one" and the Jira admin can then verify the use case of the new project by looking at the Project Category of that referenced project.
This particular Jira instance has over 1850 projects and just about 1.5 million issues so it was important to keep things under control. This approach has worked very well even though it is not flawless :)
Hope this helps someone :)