Skip to main content

Issue Operations

1. Scenario Description​

Assign requirements/tasks by editing issue attributes such as assignee; break down requirements/tasks by creating sub-issues; track the execution of requirements/tasks through status transitions.

2. Main Features​

  • Select the corresponding issue and hover to click for related operations. Such as: edit, delete, create sub-issue, copy, migrate, and other operations
  • Open in new tab: Open a new tab to view
  • Copy link: Copy the issue link to share for viewing
  • Edit: Edit the field attribute information of the issue
  • Create sub-issue (quick create sub-issue): This button is only available when the issue can create sub-issues. Issues filtered across workspace panels do not have the create sub-issue button; you need to open the details page to create sub-issues
  • Delete: When deleting an issue, sub-issues will be deleted together. Operate with caution!
  • Copy: Copy the issue
  • Migrate issue: Migrate the issue to another workspace or change the issue type. Migration must follow the target workspace hierarchy scheme to succeed
  • Urge issue: Remind corresponding users to handle through urging

3. Copy Feature​

  • Click "Copy" to open the above dialog
  • Title defaults to the title of the copied issue and can be modified
  • Title defaults to "Copy [copied card title]" and can be modified
  • Status: Initial status is selected by default, and the copied issue will have initial status If "Sync issue status" is selected, the copied issue status will be consistent with the copied card's status
  • Copy content: By default, the copied issue maintains consistency with the source issue's workspace, type, and fields, and only copies field content. Issue hierarchy, issue associations, attachments, time logs, and other content are not copied
  • The copied issue belongs to the same hierarchy level as the source issue. For example, in A-B-C hierarchy, after copying A, the copied issue will be at the same level 1 as A. If copying B, the copied issue will be at the same level as B and be a sub-level of A.
  • Change record: For copied cards, the change record shows "xx copied issue [copy time]"
  • Status transition: If it's initial status, it shows the initial status process. If syncing issue status, the status transition shows nodes from initial status to current status according to the copied card's process, with creator as "System"
  • The copied issue establishes an association relationship with the copied issue by default

4. Issue Details​

Click on the issue details page to perform operations such as follow, full-screen view, copy link, etc.

At the bottom, you can view the issue's change records and transition records, as well as corresponding comments