field-settings_skill

Overview

This skill exposes Meegle OpenAPI endpoints to read, create, and update work item field settings in a space. It lets you list field metadata, create custom fields of many types, and modify field configuration including options and permissions. Token and domain are required for authenticated requests.

How this skill works

The skill calls three endpoints: get_field_information to retrieve all fields (option lists and compound sub-fields included), create_custom_field to add a new custom field and return its field_key, and update_custom_field to change an existing custom field by field_key. Requests require plugin/user headers and the project_key (space ID or simple_name) and follow the Meegle field schema for field_type_key, field_value, team_option, and other attributes.

When to use it

• Build dynamic field selectors or form UIs that need field keys, types, aliases, and option lists
• Add a new custom field (text, select, date, user, number, link, multi_file, bool, relationship types, etc.) to a work item type
• Reuse option sets from an existing field or define new option lists for select-type fields
• Update option lists, default values, help text, authorized roles, or team-scoped cascading options
• Resolve field_key values required by other APIs (e.g., schedule_field_key or custom payloads)

Best practices

• Always call get_field_information first to obtain accurate field_key and field_type_key before create/update operations
• For select/tree fields choose either field_value (custom options) or team_option (team-scoped cascading options), never both
• Use value_type = 1 with reference_work_item_type_key and reference_field_key when you want to reuse another field's options
• Provide work_item_relation_uuid for relationship-type fields when creating or updating related selects
• Handle error codes for duplicates and concurrent updates (field_name/alias conflicts and invalid update version)

Example use cases

• Populate a project UI selector with all available fields and option labels/values for a given work item type
• Create a custom priority select with predefined options and a default value for a specific work item type
• Update an existing multi-level tree select to add a sub-option (include parent_value when adding sub-options)
• Change help text and authorized_roles for a sensitive custom field to restrict who can edit it
• Migrate or sync option sets between fields by creating a new field with value_type = 1 referencing the source field