Skip to content

docs: rewrite work item copy section for the unified copy flow - #480

Open
sriramveeraghanta wants to merge 3 commits into
masterfrom
docs/work-item-copy-behavior
Open

docs: rewrite work item copy section for the unified copy flow#480
sriramveeraghanta wants to merge 3 commits into
masterfrom
docs/work-item-copy-behavior

Conversation

@sriramveeraghanta

@sriramveeraghanta sriramveeraghanta commented Jul 28, 2026

Copy link
Copy Markdown
Member

Description

Updates the Duplicate work items section of core-concepts/issues/overview to match the copy behavior that shipped recently. The "Copy in same project / Copy in different project" submenu has been replaced by a single Make a copy modal with a destination project picker, and the same-project and cross-project paths now follow one consistent spec.

The existing section documented the old submenu and was wrong about the behavior in both directions:

  • It said a same-project copy "maintains the same title" — the title now gets a (Copy) suffix.
  • It described a cross-project copy as only adapting "the destination project's identifier format and default state", while omitting that assignees, labels, modules, cycle, estimate, and every custom property value are cleared. That omission is the part users would actually get burned by.

What changed

  • One flow, not two — the ### Copy in same project / ### Copy in different project sub-sections are gone, replaced by a description of the single modal with its destination picker defaulting to the current project.
  • A comparison table covering every field, same project vs. different project. The two cases differ enough that prose would bury it.
  • A one-line rationale for the cross-project clearing (labels, modules, cycles and estimates are project-scoped), so it reads as a design decision rather than a gap.
  • A tip on the custom-properties-into-description fallback, since users would otherwise assume the values vanished.
  • Notes and limits — the epic constraint on cross-project copies, archived items copying as active, and a pointer to bulk operations.
  • Mentions the Duplicate of backlink relation.

Not covered here

Two things I deliberately left out, flagging for a reviewer's call:

  1. This section carries a Pro badge and documents the Pro behavior only. Community projects still use the older prefilled-create-modal flow, which behaves differently — that may warrant its own note.
  2. core-concepts/issues/bulk-ops doesn't list copy among its bulk operations at all. Now that bulk copy shares the same semantics, that page is arguably missing an entry — linked to from here, but not edited, as it was outside the scope of this change.

Anchors

#copy-in-same-project and #copy-in-different-project no longer exist. Nothing in the source tree links to them (grepped), but external inbound links will now land at the page top rather than the section.

Verification

pnpm fix:format runs clean.

plane-ee#8543 replaced the "Copy in same project / Copy in different
project" submenu with a single "Make a copy" modal with a destination
project picker, and reconciled three divergent copy implementations
against one spec.

The existing section documented the old submenu and was wrong about
behavior in both directions: it claimed a same-project copy keeps the
title (it now gets a "(Copy)" suffix), and described a cross-project
copy as only adapting the identifier and default state while omitting
that assignees, labels, modules, cycle, estimate and custom property
values are all cleared.

Replaces the two sub-sections with a same-vs-different comparison table
covering every field in the PR's spec, a note on why project-scoped
fields cannot cross the boundary, the custom-properties-into-description
fallback, and the epic / archived-item limits.

Drops the #copy-in-same-project and #copy-in-different-project anchors.
Nothing in the source tree links to them.

Claude-Session: https://claude.ai/code/session_01Tjjd2h2NfSWbhnMn1EKGj2
@vercel

vercel Bot commented Jul 28, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
docs Ready Ready Preview, Comment Jul 28, 2026 12:17pm

Request Review

@coderabbitai

coderabbitai Bot commented Jul 28, 2026

Copy link
Copy Markdown

Review Change Stack

📝 Walkthrough

Walkthrough

Changes

Work item copy documentation

Layer / File(s) Summary
Copy flow and behavior rules
docs/core-concepts/issues/overview.md
Documents the “Make a copy” flow, destination project selection, copied fields, cross-project custom property handling, duplicate relationships, and eligibility and bulk-copy constraints.

Estimated code review effort: 2 (Simple) | ~10 minutes

Suggested reviewers: danciaclara

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly reflects the main documentation change: rewriting the work item copy section for the unified copy flow.
✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/work-item-copy-behavior

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/core-concepts/issues/overview.md`:
- Line 141: Update the duplicate-section statement in
docs/core-concepts/issues/overview.md so it does not claim bulk copying follows
documented single-copy rules unless docs/core-concepts/issues/bulk-ops.md is
expanded to cover Make a copy and its rules; prefer either adding that complete
bulk-copy documentation or changing the linked text to a general bulk-operations
overview.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: d3a42baf-b49e-4070-9afc-60b65dffde13

📥 Commits

Reviewing files that changed from the base of the PR and between f3804cb and d15c728.

📒 Files selected for processing (1)
  • docs/core-concepts/issues/overview.md

Comment thread docs/core-concepts/issues/overview.md Outdated
Two errors in one line. The guard in _resolve_copy_type only runs on the
cross-project branch — same-project copies return original_issue.type
before it is reached — so the limit is not the blanket rule the note
implied. And "skipped" described bulk behavior: the single-item
duplicate endpoint returns 400 with "Epics are not enabled for the
selected project", so the user gets an error and no copy.

Splits the two cases and moves the skip-and-continue behavior to the
bulk bullet, which is the only place it applies.

Claude-Session: https://claude.ai/code/session_01Tjjd2h2NfSWbhnMn1EKGj2
The duplicate section pointed at bulk-ops as the reference for bulk
copying, but that page never mentioned Make a copy at all — the link
landed on a page with no copy content.

Adds a Copy work items section covering the bulk-specific parts (the
1000-item cap, create permission in the destination, the background
run, and epics being skipped in a mixed selection), deferring the
field-by-field rules to the table in the duplicate section rather than
duplicating them. Retargets the overview link at that section.

Claude-Session: https://claude.ai/code/session_01Tjjd2h2NfSWbhnMn1EKGj2
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants