kd-cli 2.5.0__tar.gz → 2.5.1__tar.gz

{kd_cli-2.5.0/kd_cli.egg-info → kd_cli-2.5.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: kd-cli
-Version: 2.5.0
+Version: 2.5.1
 Summary: Knowledge Dispatcher for issue trackers and knowledge bases
 Author: Sergiy Gladkyy
 License-Expression: MIT

{kd_cli-2.5.0 → kd_cli-2.5.1}/kd/cli/namespaces/issue/__init__.py

@@ -270,11 +270,20 @@ class IssueCreateCommand(Command):
             "Create an issue",
             requires_client=True,
             usage='kd /issue create "Summary" --project P [--field NAME=VALUE] [--attach FILE]',
-            long_description="Summary is the issue title. --project is the project key (e.g. FB).",
+            long_description=(
+                "Summary is the issue title. --project is the project key (e.g. FB). "
+                "--field NAME=VALUE supports bundle families (enum, state, owned, "
+                "version, build), user logins, period, and string custom fields; the "
+                "field name is fuzzy-matched and the value is passed verbatim. "
+                "Unsupported families (text, Multi*, and integer/float/date subtypes "
+                "of SimpleProjectCustomField) fail client-side with an error naming "
+                "both the project $type and fieldType.id subtype."
+            ),
             examples=[
                 'kd /issue create "Fix router config" --project FB --type Task',
                 'kd /issue create "Bug report" -p FB --attach screenshot.png --attach log.txt',
                 'kd /issue create "Sprint task" -p FB --field "Sprint=Sprint 47"',
+                'kd /issue create "Tracked" -p VIS --field "Milestone=M039"',
                 'kd /issue create "Design doc" -p FB --description @design.md',
             ],
             see_also=["/issue list", "/issue show", "/issue/attachment add", "/project/field list"],
@@ -437,10 +446,21 @@ class IssueUpdateCommand(Command):
             "Update an issue",
             requires_client=True,
             usage="kd /issue update ID [--title T] [--field NAME=VALUE]",
+            long_description=(
+                "--field NAME=VALUE supports bundle families (enum, state, owned, "
+                "version, build), user logins, period, and string custom fields; the "
+                "field name is fuzzy-matched and the value is passed verbatim. "
+                "Clear optional custom fields with NAME= (empty value). Unsupported "
+                "families (text, Multi*, and integer/float/date subtypes of "
+                "SimpleProjectCustomField) fail client-side with an error naming "
+                "both the project $type and fieldType.id subtype."
+            ),
             examples=[
                 'kd /issue update FB-42 --title "New title"',
                 "kd /issue update FB-42 --state Open --priority Critical",
                 'kd /issue update FB-42 --field "Sprint=Sprint 48"',
+                'kd /issue update VIS-21 --field "Milestone=M039"',
+                'kd /issue update FB-42 --field "Milestone="',
                 "kd /issue update FB-42 --description @updated.md",
             ],
             see_also=["/issue show", "/project/field list"],

{kd_cli-2.5.0 → kd_cli-2.5.1}/kd/client.py

@@ -22,6 +22,7 @@ import builtins
 import difflib
 import shlex
 from collections import OrderedDict
+from collections.abc import Callable
 from dataclasses import dataclass, field as dataclass_field
 from datetime import datetime, timezone
 from pathlib import Path
@@ -130,15 +131,43 @@ def _resolve_link_command(link_type: str) -> str:
     return result
 
 
-# Maps project custom field $type to the $type needed for issue mutations.
-_PROJECT_TO_ISSUE_TYPE: dict[str, str] = {
-    "EnumProjectCustomField": "SingleEnumIssueCustomField",
-    "StateProjectCustomField": "StateIssueCustomField",
-    "UserProjectCustomField": "SingleUserIssueCustomField",
-    "OwnedProjectCustomField": "SingleOwnedIssueCustomField",
-    "VersionProjectCustomField": "MultiVersionIssueCustomField",
-    "BuildProjectCustomField": "SingleBuildIssueCustomField",
-    "PeriodProjectCustomField": "PeriodIssueCustomField",
+# Dispatch over (project_field_type, field_type_id) → (issue_type, payload_builder).
+#
+# The builder wraps a validated value into the exact shape YouTrack expects in
+# the ``customFields[].value`` slot of an issue create/update payload. Bundle
+# families wrap as ``{"name": ...}``; user fields wrap as ``{"login": ...}``;
+# the scalar simple-string family passes through verbatim.
+#
+# ``""`` as the second tuple element means "any field_type_id under this
+# ``$type``" — used when every subtype of a family shares one payload shape.
+# A specific ``field_type_id`` key wins over the wildcard when both are present
+# (see ``SimpleProjectCustomField`` which only supports the ``string`` subtype
+# this session; ``integer``/``float``/``date`` stay unmapped).
+
+FieldValueBuilder = Callable[[str], Any]
+
+
+def _bundle_name(value: str) -> dict[str, str]:
+    return {"name": value}
+
+
+def _user_login(value: str) -> dict[str, str]:
+    return {"login": value}
+
+
+def _scalar(value: str) -> str:
+    return value
+
+
+_FIELD_DISPATCH: dict[tuple[str, str], tuple[str, FieldValueBuilder]] = {
+    ("EnumProjectCustomField", ""): ("SingleEnumIssueCustomField", _bundle_name),
+    ("StateProjectCustomField", ""): ("StateIssueCustomField", _bundle_name),
+    ("UserProjectCustomField", ""): ("SingleUserIssueCustomField", _user_login),
+    ("OwnedProjectCustomField", ""): ("SingleOwnedIssueCustomField", _bundle_name),
+    ("VersionProjectCustomField", ""): ("MultiVersionIssueCustomField", _bundle_name),
+    ("BuildProjectCustomField", ""): ("SingleBuildIssueCustomField", _bundle_name),
+    ("PeriodProjectCustomField", ""): ("PeriodIssueCustomField", _bundle_name),
+    ("SimpleProjectCustomField", "string"): ("SimpleIssueCustomField", _scalar),
 }
 
 # Default target field names for semantic CLI slots.
@@ -274,14 +303,10 @@ class FieldSchema:
             self._debug.debug("fields", f"resolving slot '{slot}' -> target '{target_name}'")
 
             field = self._find_field(project_fields, target_name, slot)
-            issue_type = _PROJECT_TO_ISSUE_TYPE.get(field.project_field_type)
-            if not issue_type:
-                raise ValidationError(
-                    f"Unsupported field type '{field.project_field_type}' for field '{field.name}'"
-                )
+            issue_type, builder = self._resolve_dispatch(field)
 
             validated_value = self._validate_field_value(field, value)
-            field_value = self._field_value_payload(field, validated_value)
+            field_value = builder(validated_value) if validated_value is not None else None
             self._debug.debug(
                 "fields",
                 f"resolved '{slot}' -> field '{field.name}' ($type={issue_type})",
@@ -342,13 +367,9 @@ class FieldSchema:
         """
         project_fields = self.get_fields(project_id)
         field = self._find_field_fuzzy(project_fields, field_name)
-        issue_type = _PROJECT_TO_ISSUE_TYPE.get(field.project_field_type)
-        if not issue_type:
-            raise ValidationError(
-                f"Unsupported field type '{field.project_field_type}' for field '{field.name}'"
-            )
+        issue_type, builder = self._resolve_dispatch(field)
         validated_value = self._validate_field_value(field, value)
-        field_value = self._field_value_payload(field, validated_value)
+        field_value = builder(validated_value) if validated_value is not None else None
         self._debug.debug(
             "fields",
             f"resolved generic '{field_name}' -> field '{field.name}' "
@@ -388,19 +409,30 @@ class FieldSchema:
         """Return True if this field is a user-type field (user[1])."""
         return field.field_type_id.startswith("user")
 
-    def _field_value_payload(
-        self,
+    @staticmethod
+    def _resolve_dispatch(
         field: ProjectCustomField,
-        value: str | None,
-    ) -> dict[str, str] | None:
-        """Build the YouTrack issue-field value payload.
-
-        ``None`` is a deliberate clear operation and must serialize as
-        ``"value": null`` in the final issue mutation payload.
+    ) -> tuple[str, FieldValueBuilder]:
+        """Look up the issue-side ``$type`` and payload builder for *field*.
+
+        Prefers an exact ``(project_field_type, field_type_id)`` key, then
+        falls back to the wildcard ``(project_field_type, "")`` key for
+        families where every subtype shares a payload shape. Unmapped
+        combinations raise a ``ValidationError`` naming both identifiers so
+        a follow-on ticket has the upstream type info it needs.
         """
-        if value is None:
-            return None
-        return {"login": value} if self._is_user_field(field) else {"name": value}
+        key = (field.project_field_type, field.field_type_id)
+        if key in _FIELD_DISPATCH:
+            return _FIELD_DISPATCH[key]
+        wildcard = (field.project_field_type, "")
+        if wildcard in _FIELD_DISPATCH:
+            return _FIELD_DISPATCH[wildcard]
+        raise ValidationError(
+            f"Unsupported custom field type '{field.project_field_type}' "
+            f"with subtype '{field.field_type_id}' for field '{field.name}'. "
+            "kd does not know how to build a safe value payload for this "
+            "YouTrack field family."
+        )
 
     def _validate_field_value(
         self,
@@ -421,7 +453,7 @@ class FieldSchema:
         if self._is_user_field(field):
             return value  # User fields: server validates against group members
         if not field.bundle_values:
-            return value  # Freeform field (period, text) — accept as-is
+            return value  # Freeform family (period or scalar string) — server validates
 
         # Case-insensitive exact match → return canonical name
         value_lower = value.lower()
@@ -684,7 +716,7 @@ class IssueOperations:
             if "=" not in pair:
                 raise ValidationError(f"Invalid field format: '{pair}'. Expected NAME=VALUE")
             name, value = pair.split("=", 1)
-            cf = self._field_schema.resolve_field(project_obj.id, name.strip(), value.strip())
+            cf = self._field_schema.resolve_field(project_obj.id, name.strip(), value)
             result.append(cf)
         return result
 

{kd_cli-2.5.0 → kd_cli-2.5.1}/kd/resources/CHANGELOG.md

@@ -4,6 +4,14 @@ All notable changes to kd-cli are recorded here. The project follows [Semantic V
 
 ## [Unreleased]
 
+## [2.5.1] — 2026-04-19
+
+### Fixed
+- `kd /issue create --field NAME=VALUE` and `kd /issue update --field NAME=VALUE` now accept **string custom fields**. Before: `kd /issue update VIS-21 --field Milestone=M039` rejected with `Error: Unsupported field type 'SimpleProjectCustomField' for field 'Milestone'`, blocking workflows that track freeform per-issue metadata such as a rolling milestone string. `--field "NAME="` clears an optional string field just like it clears enum/user fields today; required string fields reject empty values with the same client-side error shipped in 2.2.2. Whitespace inside the value is preserved — `--field "Milestone=  M 039  "` sends `  M 039  ` verbatim. Only the field **name** is trimmed (KDCLI-106).
+
+### Changed
+- Unsupported custom-field errors now name both identifiers and the cause. Before: `Error: Unsupported field type 'X' for field 'Y'`. Now: `Error: Unsupported custom field type 'X' with subtype 'Y' for field 'Z'. kd does not know how to build a safe value payload for this YouTrack field family.` Applies to YouTrack text fields, multi-arity enum/user variants, and integer/float/date simple-field subtypes — paste the message into a bug report and the two type identifiers are already there (KDCLI-106).
+
 ## [2.5.0] — 2026-04-19
 
 Dogfooding friction fixes across tag and article workflows, plus self-describing `/system info` output for bug reports. Focus of this release: the taxonomy and article-create loops now behave the way field use expects, and a paste of `kd /system info -o yaml` replaces hand-typed version footers.

{kd_cli-2.5.0 → kd_cli-2.5.1}/kd/resources/operating-guide.md

@@ -108,6 +108,8 @@ kd /project/field list KDCLI
 
 Clear optional custom fields with an empty value, for example `kd /issue update KDCLI-42 --field "Milestone="`. Required fields reject empty values before any upstream write.
 
+`--field` supports bundle families (enum, state, owned, version, build), user fields, period, and string `SimpleProjectCustomField` subtypes; whitespace inside the value is preserved. Unsupported families (text, `Multi*` enum/user variants, and `SimpleProjectCustomField` with `integer` / `float` / `date` subtypes) fail client-side with a message naming both the project `$type` and the `fieldType.id` subtype so a follow-on bug report can skip the probe.
+
 Attachment metadata download URLs may start with `/api/`. kd handles this internally on download commands; do not assume the raw URL can be appended unchanged to an API base URL in custom scripts.
 
 Tag existence, tag visibility, and tag sharing rights are different concerns. A visible tag may not be usable for every operation, and sharing settings are provider-specific security posture, not just display metadata.

{kd_cli-2.5.0 → kd_cli-2.5.1/kd_cli.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: kd-cli
-Version: 2.5.0
+Version: 2.5.1
 Summary: Knowledge Dispatcher for issue trackers and knowledge bases
 Author: Sergiy Gladkyy
 License-Expression: MIT

{kd_cli-2.5.0 → kd_cli-2.5.1}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "kd-cli"
-version = "2.5.0"
+version = "2.5.1"
 description = "Knowledge Dispatcher for issue trackers and knowledge bases"
 readme = "README.md"
 requires-python = ">=3.11"