Jira Service Management の管理者向けの利用開始ガイド
最初に、Jira Service Management の使用を開始する方法を確認します。
As of 16 October 2024, usage limits will apply to Assets and the virtual service agent in Jira Service Management. See our blog article for more details.
Optimizing your schemas in Jira Service Management (JSM) is essential for effective asset management. Well-structured schemas help you manage many objects efficiently, keeping your system scalable and easy to maintain. This guide provides best practices for organizing your schemas to maximize the use of your objects. Usage limits and how they work for Assets.
Best Practices for Structuring Schemas
Define Clear Object Types and Attributes
Object Types: Clearly define different types of objects, like hardware, software, and licenses. This categorization helps manage assets efficiently.
Attributes: Specify attributes for each object type to capture important details. For example, a hardware object might have attributes like serial number, purchase date, and warranty period.
Use Hierarchical Structures
Hierarchy: Organize object types hierarchically to reflect real-world relationships. For example, a computer object type might include child types like monitors and peripherals. This maintains a logical and clear structure.
Optimize Schema Design
Minimize Redundancy: Avoid repeating data across object types. Instead, use references and relationships to link related objects.
Reuse Object Types: Reuse existing object types when possible, rather than creating new ones. This reduces complexity and simplifies schema management.
Implement Naming Conventions
Consistency: Adopt consistent naming conventions for object types and attributes. This ensures clarity and makes it easier for users to understand and navigate the schema.
Leverage Object References
Relationships: Use references to connect related objects. For instance, link a software license object to the hardware it is installed on. This maintains relationships and dependencies between different assets.
Utilize Automation
Automation Rules: Set up automation rules for repetitive tasks, like automatically updating object attributes or sending notifications when certain conditions are met. This reduces manual effort and ensures data consistency.
Regularly Review and Clean Up
Periodic Review: Regularly review your schemas to remove obsolete objects and attributes, ensuring the schema stays relevant and efficient.
Data Cleanup: Regularly clean up data to eliminate duplicates and outdated information, maintaining data accuracy and reliability.
Document Your Schema
Documentation: Keep documentation for your schema design, including object types, attributes, and relationships. This aids in onboarding new team members and maintaining consistency.
この内容はお役に立ちましたか?