multica-ai/multica · warning

--value is required

Error message

--value is required

What it means

Returned by `runIssuePropertySet` when `--value` was never changed on the command line (`cmd.Flags().Changed("value")` is false). Note it requires the flag to be explicitly present — a defaulted empty value is not accepted — because the set operation is meaningless without a value.

Source

Thrown at server/cmd/multica/cmd_property.go:614

	if err != nil {
		return err
	}
	rows := buildIssuePropertyRows(properties, bag)
	output, _ := cmd.Flags().GetString("output")
	if output == "json" {
		return cli.PrintJSON(os.Stdout, rows)
	}
	printIssuePropertyRows(rows)
	return nil
}

func runIssuePropertySet(cmd *cobra.Command, args []string) error {
	name, _ := cmd.Flags().GetString("name")
	if name == "" {
		return fmt.Errorf("--name is required")
	}
	if !cmd.Flags().Changed("value") {
		return fmt.Errorf("--value is required")
	}
	rawValue, _ := cmd.Flags().GetString("value")

	client, err := newAPIClient(cmd)
	if err != nil {
		return err
	}
	ctx, cancel := cli.APIContext(context.Background())
	defer cancel()

	issueRef, err := resolveIssueRef(ctx, client, args[0])
	if err != nil {
		return fmt.Errorf("resolve issue: %w", err)
	}
	properties, err := fetchProperties(ctx, client)
	if err != nil {
		return err
	}

View on GitHub (pinned to 2c0912b6ec)

Solutions

1. Always pass `--value <something>` when setting.
2. To clear a property, use `multica issue property unset <issue> --name <prop>` instead.
3. In scripts, branch: if the value variable is empty, call unset; otherwise call set.

Example fix

// before
multica issue property set ISS-1 --name Priority
// error: --value is required

// after (clear)  : multica issue property unset ISS-1 --name Priority
// after (set)    : multica issue property set ISS-1 --name Priority --value P1

# bash: branch on emptiness — unset when clearing, set when provided
if [ -z "$VAL" ]; then multica issue property unset "$ISSUE" --name "$PROP_NAME"; else multica issue property set "$ISSUE" --name "$PROP_NAME" --value "$VAL"; fi

When it happens

Trigger: Running `issue property set` with `--name` but no `--value`; note that even `--value ""` satisfies Changed() but then fails later in value encoding for typed properties.

Common situations: Users expect set with only `--name` to clear a value; scripts conditionally omit `--value` when a variable is empty.

Related errors

• --%s, --%s-stdin, and --%s-file are mutually exclusive; pick
• --%s-file: path must not be empty
• --runtime-id must not be empty
• --name must not be empty
• --max-concurrent-tasks %w (got %d)

AI-assisted analysis of multica-ai/multica@2c0912b6ec (2026-08-15). Data as JSON: /api/errors/722fbea4864b4830. Report an issue: GitHub.