multica-ai/multica · error

issue %s has no status, cannot determine its column

Error message

issue %s has no status, cannot determine its column

What it means

Error "issue %s has no status, cannot determine its column" thrown in multica-ai/multica.

Source

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

	wsID := client.WorkspaceID
	if wsID == "" {
		wsID, err = requireWorkspaceID(cmd)
		if err != nil {
			return err
		}
	}

	issueRef, err := resolveIssueRef(ctx, client, args[0])
	if err != nil {
		return fmt.Errorf("resolve issue: %w", err)
	}
	target, err := fetchIssue(ctx, client, issueRef.ID)
	if err != nil {
		return fmt.Errorf("get issue: %w", err)
	}
	status := strVal(target, "status")
	if status == "" {
		return fmt.Errorf("issue %s has no status, cannot determine its column", issueRef.Display)
	}

	// Resolve the relative target up front, before any no-op shortcut, so a bad
	// --before/--after value (typo, self-reference) always errors instead of
	// being swallowed by the single-issue-column fast path below.
	relative := before != "" || after != ""
	var otherRef resolvedID
	if relative {
		otherInput := before
		if after != "" {
			otherInput = after
		}
		otherRef, err = resolveIssueRef(ctx, client, otherInput)
		if err != nil {
			return fmt.Errorf("resolve target issue: %w", err)
		}
		if otherRef.ID == issueRef.ID {
			return fmt.Errorf("cannot reorder issue %s relative to itself", issueRef.Display)

View on GitHub (pinned to 2c0912b6ec)

Solutions

1. Set a status on the issue first with 'multica issue status'.

When it happens

Trigger: Thrown at server/cmd/multica/cmd_issue.go:1572 when the library encounters an invalid state.

Common situations: See trigger scenarios.

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