Skip to main content
Skip table of contents

Creating, copying, or deleting an issue

Creating an issue 

You can create three types of issue, depending on the relationship with the original issue.

Copy and Paste

You can duplicate a source issue, or a source issue and all its subordinate issues.

To create from the contextual menu

  1. Right-click on the issue you want to duplicate.

  2. Select Copy & PasteThis issue or This issue and all child issues.

To create from the operations toolbar

  1. Select the issue you want to duplicate.

  2. Select Add ⇒ This issue or This issue and all child issues on the operations toolbar.

Successor issues

This is when an issue is created with the original issue set as a predecessor issue. 

The process is as follows:

  • A dependency line is drawn from the issue of the selected node.

  • The next business day after the planned finish date in the selected node of the issue is set as the planned start date of the new issue.

Creating a successor issue from the contextual menu.

  1. Right-click the issue you want to make the predecessor issue.

  2. Select AddSuccessor issue... ⇒ Select the type of issue to be created.

Child issues

This is when a selected type of issue is created with the original issue set as a child issue.

In the sub-menu ...

  • If you select Issue, the original issue is duplicated as the selected issue type. 

  • If you select Template or Shared template, all issues subordinate to the selected template are duplicated.

To create from the contextual menu

  1. Right-click the task you want to be a parent.

  2. Select Add(Child) issue ⇒ Select the type of issue to be created.

To create from the operations toolbar

  1. Select the task you want to be a parent.

  2. Select Add  ⇒ Select the type of issue to be created on the toolbar.

If the issue type of the parent issue is Epic, the hierarchical relationship is created using Epic links.

Therefore, it must be possible to set a value in the epic link field of the child issue.

The issue type of the issue that will be the child issue must display an epic link field on the issue creation screen.

To create from the issue navigator screen 

  1. Display the issue navigator screen of the issue you want to be a parent.

  2. Select ○○ Create on the toolbar or  ○○ Create in the WBS Gantt-Chart section.

These menus or links may be hidden by (project) administrator.

Creating an issue from an issue template

Changing an issue summary and description on an issue template

When Template or Shared Template is selected, you can replace “$<Any string>$” in the issue summary and description (under Template) with a text of your choice. 

Adjusting the planned dates of an issue template

If you select Template or Shared template, create an issue by adjusting the planned date and due date set in the issue template according to the planned start date of the original issue.

Also, even if the planned start date is not set for the original issue, we adjust the planned date and due date according to issue creation date and create an issue. However, the above is only applicable if you can set an issue creation date in the planned date at issue creation. 

Fields configured when issues are created

When issues are created values are set according to the following criteria:

  • System fields are copied from the original issues

    • Set default values are related to workflow (for example, status, resolution) 

  • Custom fields are not copied

    • Planned dates are copied from the original issues

Deleting an issue

To delete from the contextual menu

  1. Right-click on the issue you want to delete.

  2. Delete ... ⇒ Select This issue, or This issue and all child issues.

  3. Select Yes in the delete confirmation dialog.

To delete from the operations bar

  1. Select the issue you want to delete

  2. Delete on the toolbar ⇒ Select This issue, or This issue and all child issues.

  3. Select Yes in the delete confirmation dialog.

If you select This issue and delete an issue with a subordinate issue, the subordinate issue will not be displayed. Please reload WBS Gantt-Chart to see it again.

Issues displayed in gray font (displayed in order to preserve the hierarchy structure) cannot be deleted.

Changing the structure of an issue 

To change the structure with drag-and-drop

You can arbitrarily change the structure of an issue by rearranging it using sort with drag-and-drop.

To change the structure through the operations bar

The process is as follows: 

  1. Select the task you want to change

  2. Click Edit on the operations bar

  3. Select Indent or Outdent
    Indent changes the hierarchy down one step (i.e. it makes an issue the child of the one above it). Outdent is the reverse of this. It changes the hierarchy up one step. 

To change the structure with keyboard shortcuts

  1. Select the task you want to change

  2. To Indent (changes hierarchy down one step), press Alt + →  (Alt + Shift + → for Mozilla-based browsers). 

    To Outdent (changes hierarchy up one step), press  Alt + ←  (Alt + Shift + ← for Mozilla-based browsers).

Note

The hierarchy link and fix version changes according to the changes you make and where you move the issue. 

Target

Hierarchy link

Fix version

Project

Cancels all

Deletes all

Version

Cancels all

Changes to version of dropped-on issue

Issue

Changes to issue which is dropped on

Changes to fix version of dropped-on issue

If the dragged issue has several fix versions, the existing fix versions are deleted, and the fix version of the dropped-on issue is selected.

Drag and drop is not possible under the following circumstances:

  • When a hierarchy link cannot be formed by the combination;

  • When a dragged issue or dropped-on issue cannot be edited;

  • When a dragged issue has a dependent issue which is a parent or a child of the dropped-on issue.


Additional Help

If you have any questions please feel free to ask a member of the Atlassian community!

Add the tag "addon-jp.ricksoft.plugins.wbsgantt-for-jira" when you ask a question.

Ask the community

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.