Creating an Issue in Jira

Issue : An Issue in Jira represent the piece of work in the project, it may anything which includes a Task, a Bug and a Story.

Issues typically represent the user requirements, software bugs and a feature, An issue may also contain the subtask, it can be assigned to and tracked by individually

Let us see how to create an issue:

First, Login to your Jira account using your credentials and then on the left corner you can see a "+" mark, just click on that, you are promoted to create an issue, then select the relevant project type and an issue type.

Here I selected Issue type as Epic for scrum project and then click on the Next, jira will take you to create issue page, fill required paths and click on the Create Button at the Bottom.

So you have created an issue called Epic1, just click on the Issue name you can see the details of that issue.

The same way you can also create a defect called Bug and also a story too.

And Once you are done with creating an issue you can search for the issue and you can see all the details. Any issues which are created may be a story, a Bug and a Task, During the course of the time, we need to check the status of the project.

Workflow: In Jira, there is a workflow, which is the main backbone of Jira, any issue which is created either it is a bug, epic or story is created is having a status that means we need to check whether it is closed or done or any developer is working on it or issue cannot be solved due to some blocker our project is configured here.

If the issue is resolved it will show you as done, if still, it is in progress then it will show you it is In Progress and if an issue is new and nobody is currently working on it, then it will show you as To Do

Priority : Priority tells Developer to fix the issue according to the range of priority ticket, that means If the priority is High, that means the developer needs to fix the issue first, let us say, there is a defect that user is unable to login and another one defect where the spelling of log in is incorrect.

So if you compare these two issues the first issue is on high priority and developer has to fix that issue first.

Assignee: Assignee is the one to whom we asked to work on it.

Reporter: Whos has reported this to the developer to solve the issue.

Comment: In the comment section you add any comment related to the issue and anything which is related to the project, challenges you are facing to solve these issues.

Cloning an Issue

cloning an issue will create the duplicate of an issue within the same project, as it contains most of the same details from the original issue like summary, Affects, versions, and components except the details like comments, history, worklog, etc..

The cloned history can be linked to the original issue. Now let us see how to clone an issue step by step as follow:

Open the main page and click on the jira settings, you can see the product, projects, system, and issues.

click on the issues, then you can see issue type, just click on the issue type, on the right side you can see the issue with the project name and the summary as shown below.
So, on the right corner sude you will see three dots, just click on that, it will suggest you the different options like log time, add flog, move and clone.
Select the clone option, now the clone issue page will appear.

You can edit the cloning summary in case if you want to do that and click on the create, the cloned issue page will now be created as shown below.

Convert to Subtask

To complete the work in a small time, we can divide the issues into smaller parts and assign them to the team members, we call it as a Subtask.

We can covert an issue to subtask as follow

Go to the main menu of Jira software and click on Issues and Filter then it will navigate you to Search Issues, click on that, it will show you all the issues which we are created.

Click on three dots(...) on the right corner, select the convert subtask under that.

  • Select the parent issue type and subtask type.
  • Select the issue type from the issue selector and click next.
  • Once you click on the Next, it will ask you to update the fields of the issue to relate to the new issue type otherwise, you will see a message as all the fields will be updated automatically, and then click Next.
  • The last step will show you all the details of for issue, if you are satisfied with the values then click Finish.
    Now, it will display the subtask and the parent issue number has been displayed with that, here the SSP-1 is the parent issue type.

Converting a subtask to an Issue

The same way we have done converting an Issue to the Subtask, we can also convert a Subtask to an Issue.

  • Navigate to the Subtask you would like to convert it to an Issue.
  • Click on three dots(...) on the right corner, select the convert Issue under that.
  • The first step here is to select the Issue type, as it may be a Story, a Task, Bug, and an Epic, here I selected a Story and then click Next.
  • Next, it will ask you to update the fields of the issue to relate to the new issue type and ask you to enter the story points, that means it is the measurement of the complexity of the size of the requirement and hence I gave it has 2 for demo purpose.
Comment / Suggestion Section
Point our Mistakes and Post Your Suggestions