multica-ai/multica · error

--title is required

Error message

--title is required

What it means

`multica issue create` was run without a usable --title; the flag is empty and the CLI refuses to create a titleless issue. This is the first check in runIssueCreate, before any validation or API call, so nothing is sent to the server.

Source

Thrown at server/cmd/multica/cmd_issue.go:1070

	return out
}

func quickCreateAttachmentIDsFromEnv() ([]string, error) {
	raw := strings.TrimSpace(os.Getenv("MULTICA_QUICK_CREATE_ATTACHMENT_IDS"))
	if raw == "" {
		return nil, nil
	}
	var ids []string
	if err := json.Unmarshal([]byte(raw), &ids); err != nil {
		return nil, fmt.Errorf("parse MULTICA_QUICK_CREATE_ATTACHMENT_IDS: %w", err)
	}
	return appendUniqueStrings(nil, ids...), nil
}

func runIssueCreate(cmd *cobra.Command, _ []string) error {
	title, _ := cmd.Flags().GetString("title")
	if title == "" {
		return fmt.Errorf("--title is required")
	}
	statusFlag, _ := cmd.Flags().GetString("status")
	if statusFlag != "" {
		if err := validateIssueStatus(statusFlag); err != nil {
			return err
		}
	}
	priorityFlag, _ := cmd.Flags().GetString("priority")
	if priorityFlag != "" {
		if err := validateIssuePriority(priorityFlag); err != nil {
			return err
		}
	}

	client, err := newAPIClient(cmd)
	if err != nil {
		return err
	}

View on GitHub (pinned to 2c0912b6ec)

Solutions

1. Pass a non-empty --title: multica issue create --title "Fix login expiry".
2. If the value comes from a variable, guard the call: [ -n "$TITLE" ] && multica issue create --title "$TITLE" || echo 'TITLE empty' >&2.
3. Fix the upstream extraction (jq selector, grep) that was supposed to produce the title.

Example fix

# before
multica issue create --title "$TITLE"   # TITLE unset -> error
# after
: "${TITLE:?TITLE must be set to create an issue}"
multica issue create --title "$TITLE"

# fail before the CLI if the title is empty
 : "${TITLE:?TITLE must be non-empty to create an issue}"
multica issue create --title "$TITLE"

When it happens

Trigger: Running `multica issue create` with no --title at all, --title "" (explicitly empty), or --title "$TITLE" where the shell variable is unset/empty (no default word).

Common situations: Scripts forwarding an optional variable: --title "$TITLE" with set -u not in effect; automation where the upstream step that extracts a title produced nothing; interactive use expecting a prompt (the CLI does not prompt — it errors).

Related errors

• --cutoff is required; use the hosted deployment time of the
• parse --cutoff as RFC3339: %w
• --cutoff must be before now; refusing a future cutoff becaus
• --batch-size must be positive
• invalid direction %q (want \"up\" or \"down\")

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