space-setting_skill

Overview

This skill exposes Meegle OpenAPI endpoints to read space-level configuration: work item types and business line trees. It helps retrieve work_item_type_key / api_name values and full business-line structures required by other APIs and UI components. A valid plugin token and X-User-Key plus the space project_key are required before calling these APIs.

How this skill works

The skill issues GET requests against two space-scoped endpoints: /work_item/all-types to list work item types and /business/all to return the business-line tree. Responses include identifiers (type_key, api_name, id), status flags (is_disable, disabled), and nested structures (children, role_owners, watchers). Use the returned keys and IDs as inputs to other Meegle APIs and UI controls.

When to use it

• When you need work_item_type_key or api_name to call work-item, workflow, or list APIs.
• When building space configuration UIs that list or select available work item types.
• When creating business-line selectors, trees, or validation logic that require full hierarchy.
• When checking enablement flags (is_disable, enable_model_resource_lib) per work item type.
• When you must obtain role_owners, watchers, or super_masters for business-line permissions.

Best practices

• Always provide a valid X-User-Key header; missing or invalid user key returns a user-not-found error.
• Cache work item type lists and business-line trees and refresh only when configuration changes to reduce API calls.
• Use type_key or api_name from work item types as authoritative work_item_type_key in downstream API calls.
• Handle tree recursion safely: children may be nested; guard against deep recursion or cycles.
• Check permission requirements (Configuration Categories / Configuration) before calling the endpoints.

Example use cases

• Populate a dropdown of work item types (story, issue, version, sub_task) when creating a new template.
• Build a hierarchical business-line selector showing role owners and watcher counts for each node.
• Validate incoming work item payloads by mapping provided business line IDs to the returned tree.
• Conditionally enable model resource features in the UI when enable_model_resource_lib is true for a type.
• Automate migration or backup scripts that need canonical type keys and the full business-line structure.