Creating an issue

1. Select Create at the top of the screen to open the Create issue dialog box.
   
2. Select the relevant Project and Issue type in the Create issue dialog box.
3. If you’re raising a request, select the relevant Request type.
   To select a request type from the Other section, make sure you’ve selected the corresponding Issue type. How to set up request type field in the issue view
   
4. Type a Summary for the issue and complete any appropriate fields—at least the required ones that are marked by an asterisk.
5. If you want to access fields that aren't shown in this dialog box or you want to hide existing fields:
   
   1. Select the Configure fields button at the top right of the screen.
   2. Select Custom and select the fields you want to show or hide by selecting or clearing the relevant check boxes respectively, or select All to show all fields.
      When you next create an issue, these selected fields will be displayed.
6. Optional: To create a series of similar issues – with the same Project and Issue type – select the Create another checkbox at the bottom of the dialog. Depending on your configuration and the values you may have specified when creating previous issues, some of the fields in the new Create Issue dialog box may be pre-populated. Make sure you check they're all correct before creating the next issue.
7. When you're satisfied with the content of your issue, select the Create button.

Creating a linked issue

From any existing issue you're working with, you can create a linked issue between Jira Software projects or Jira Software and Jira Service Management projects. 

The linked issue will relate to the existing issue in a way you select. For example, the linked issue might block the existing one or be resolved by it. You can configure fields in the linked issue directly on the issue screen.

To create a linked issue:

1. Open an issue to which you want to link a new issue.
2. Select More, then Create linked issue.
3. In the dropdown list, select Create linked issue. The Create linked issue screen will appear.
4. On the screen, the default and custom fields reflect the fields of a destination project. The fields on the linked issue screen are pre-populated with the data from the original issue you’re viewing. You can edit them as needed.
5. After you finish working with the fields, select Create.

Cloning an issue

Cloning an issue lets you quickly create a duplicate of an issue within the same project. The cloned issue contains most of the same details stored in the original issue — e.g. Summary, Affects Versions, Components, etc. Other details aren't cloned — e.g. Work Log, Comments, Issue history, and Links to Confluence pages. The issue status also returns to the first step of the corresponding workflow, and the resolutions are cleared. The cloned issue can be linked to the original issue, but does not have to be.

Note that if you don't have the Modify reporter permission, the clone issue will be created with Reporter as the current user cloning the issue.

1. Open the issue you wish to clone.
2. Select More, then Clone. The Clone issue screen will appear.
3. You can edit the clone issue's Summary if you want.
4. If applicable to the issue you're cloning, you can also select from these options:
   • Clone sub-tasks to copy existing sub-tasks
   • Clone attachments to add any existing attachments
   • Clone links to add any existing linked issues
   • Clone sprint values to copy across the issue's current and closed sprint values
5. Select Create.

Creating a sub-task

A sub-task can be created for an issue to either split the issue into smaller chunks or to allow various aspects of an issue to be assigned to different people. If you find a sub-task is holding up the resolution of an issue, you can convert the sub-task to an issue, to allow it to be worked on independently. If you find an issue is really just a sub-task of a bigger issue, you can also convert an issue to a sub-task.

1. Navigate to the issue you would like to be the parent issue of the sub-task you are about to create.
2. Select More, then Create sub-task. You'll see the Create sub-task screen.
3. Fill in the details as needed, and then select Create at the bottom of the page.

Note that when you create a sub-task, the following values are inherited from the parent task:

• project
• issue security level
• sprint value, if any (only for Jira Software issues)

Tip: You can customize the Create sub-task screen to show fields you use most often. To do this, select Configure fields at the top right corner of the dialog, and use the All and Custom links to switch between the default screen and your custom settings. Your changes are saved for future use.

Converting a sub-task to an issue

1. Navigate to the sub-task issue you would like convert.
2. Select More, then Convert to issue.
3. In the Step 1. Select issue type screen, select a new issue type (i.e. a standard issue type) and select Next.
4. If the sub-task's current status is not an allowed status for the new issue type, the Step 2. Select new Status screen is displayed. Select a new status and select Next.
5. In the Step 3. Update Fields screen, you'll be prompted to enter any additional fields if they're required. Otherwise, you'll see the message All fields will be updated automatically. Select Next.
6. The Step 4. Confirmation screen is displayed. If you're satisfied with the new details for the issue, select Finish.
7. The issue will be displayed. You'll see that it's no longer a sub-task, that is, there's no longer a parent issue number displayed at the top of the screen.

Converting an issue to a sub-task

1. Navigate to the issue you would like to convert.
2. Select More, then Convert to sub-task.
3. In the Step 1. Select parent issue and sub-task type screen, type or select the appropriate parent issue type and the new issue type (i.e. a sub-task issue type). Select Next.
4. If the issue's current status isn't an allowed status for the new issue type, the Step 2. Select new status screen is displayed. Select a new status and select Next.
5. In the Step 3. Update fields screen, you'll be prompted to enter any additional fields if they're required. Otherwise, you'll see the message All fields will be updated automatically. Select Next.
6. The Step 4. Confirmation screen is displayed. If you're satisfied with the new details for the issue, select Finish.
7. The issue will be displayed. You'll see that it is now a sub-task, that is, its parent's issue number is now displayed at the top of the screen.

Splitting an issue

Sometimes an issue may actually be such a big chunk of work that it would be better to split it up into several issues. You can easily split your issues into several in your Kanban or Scrum backlog view. You can choose how many issues to split the original into, you can edit the summary if you need to, and if the issue is estimated, and/or in a sprint, these details can also be updated.

When you split the issue, not all fields are copied across:

To split an issue:

1. Navigate to the issue you would like to convert in your Kanban or Scrum backlog.

2. Right-select the issue in your backlog and select Split issue.

3. Make any adjustments required, you can also add additional issues here by selecting + Add another.
4. Select Split.

Once you've split your issue, the relation between the issues is maintained using issue links with the type Split to and Split from.

Restricting access to an issue

When creating (or editing) an issue, you can restrict access to that issue to members of your team who are part of a chosen security level. To be able to set the security level for an issue, your administrator must add you to the appropriate issue security level, and also grant you the 'Set Issue Security' permission for the appropriate projects. 

1. Create/edit the relevant issue.
2. In the Security level dropdown field, select the desired security level for the issue. You'll only see the security levels you belong to.
3. Save the issue. It's now only accessible to members of the specified security level.
   Users who aren't members of this security level won't be able to access that issue, or see it in any filters, queries, or statistics.