{"id":3685,"date":"2020-06-11T19:22:49","date_gmt":"2020-06-11T13:52:49","guid":{"rendered":"https:\/\/www.h2kinfosys.com\/blog\/?p=3685"},"modified":"2020-06-11T19:29:36","modified_gmt":"2020-06-11T13:59:36","slug":"how-to-create-an-issue-in-jira","status":"publish","type":"post","link":"https:\/\/www.h2kinfosys.com\/blog\/how-to-create-an-issue-in-jira\/","title":{"rendered":"How to Create an Issue in JIRA"},"content":{"rendered":"\n

JIRA issue is used to track all the work associated with a project. An issue can either be a project task, sub-task, or any other work-related to the project.<\/p>\n\n\n\n

Steps to create an issue are given below:<\/em><\/p>\n\n\n\n

Step 1<\/strong>: Click on the Create button available on the top menu bar.<\/p>\n\n\n\n

\"Issue<\/p>\n\n\n\n

Step 2:<\/strong> Choose the project and then select the issue type from the drop-down option. Fill the other fields like summary, description.<\/p>\n\n\n\n

\"https:\/\/asudev.jira.com\/wiki\/download\/thumbnails\/221905134\/image2016-3-1%2019:45:47.png?version=1&modificationDate=1456886748788&cacheVersion=1&api=v2&width=624&height=354\"<\/p>\n\n\n\n

Step 3:<\/strong> To create a similar type of issue in the same project, click on Create another checkbox.<\/p>\n\n\n\n

\"Creation<\/p>\n\n\n\n

Step 4:<\/strong> If you have not checked the option \u201cCreate another,\u201d then after clicking on the Create button, a notification will appear on the dashboard displaying the issue id and summary, which implies that the issue has been successfully created.<\/p>\n\n\n\n

\"Issue<\/p>\n\n\n\n

Step 5:<\/strong> If you have checked the option \u201cCreate another,\u201d then after clicking on the Create button, you will get a new Create Issue page displaying the issue id.<\/p>\n\n\n\n

\"Check<\/p>\n\n\n\n

You can also edit the issue or export the issue to the XML or Word document.<\/p>\n\n\n\n

Sub-task:<\/strong><\/h2>\n\n\n\n

Splitting a parent task into small chunks and assigning them to the concerned person is referred to as creating the sub-task.<\/p>\n\n\n\n

Subtasks can be created in two ways:<\/p>\n\n\n\n

  1. Create a sub-task under a parent issue.<\/li>
  2. Converting an issue to a subtask.<\/li><\/ol>\n\n\n\n

    How to create a sub-task under a parent issue?<\/strong><\/h3>\n\n\n\n

    Step 1: Open the issue where you want to create a sub-task.<\/p>\n\n\n\n

    Step 2: Click on Create Subtask.<\/p>\n\n\n\n

    Step 3: Fill all the required details.<\/p>\n\n\n\n

    \"Create<\/p>\n\n\n\n

    Step 4: Click on Create button after the form filling.<\/p>\n\n\n\n

    Workflows:<\/strong><\/h4>\n\n\n\n

    Workflows are used to track the lifecycle of an issue<\/a>. The five main stages in a workflow are:<\/p>\n\n\n\n

    1. Open Issue: After the issue is created, it is open and can be assigned to the concerned person.<\/li>
    2. Resolved Issue: When the issue has been completed by the assignee and is waiting for the reporter to be verified.<\/li>
    3. InProgress Issue: When the assignee has started working on the issue.<\/li>
    4. ReOpened Issue: When there is some mistake or error in the resolution, then it is reopened by the reporter.<\/li>
    5. Close Issue: When the issue has been fixed, and the resolution is correct and verified, then it is closed.<\/li><\/ol>\n\n\n\n

      \"Standard<\/p>\n\n\n\n

      Plug-ins in JIRA:<\/strong><\/h2>\n\n\n\n

      There are numerous plug-ins available for JIRA so that the work can be completed more efficiently. Some of the plugins are Zendesk, GitHub, Salesforce, GitBucket, etc.<\/p>\n\n\n\n

      JIRA Agile:<\/strong><\/p>\n\n\n\n

      Agile<\/a> is an iterative approach used by the development team to deliver value faster to its customers with less headache. The roadmap used by Agile Team is To Do -> In Progress -> Done.<\/p>\n\n\n\n

      How to Create Issue in Agile:<\/strong><\/h2>\n\n\n\n

      First, you need to install JIRA Agile Add-on.<\/p>\n\n\n\n

      Step 1: Create a product backlog of your Scrum or Kanban Software.<\/p>\n\n\n\n

      \"JIRA<\/p>\n\n\n\n

      Step 2: After the creation of the board, there are two modes: Plan and Work.<\/p>\n\n\n\n

      A plan mode is one where you can categorize the requirement into sprints.<\/p>\n\n\n\n

      \"JIRA<\/p>\n\n\n\n

      A work mode is one where time spent, and overall progress can be tracked.<\/p>\n\n\n\n

      \"JIRA<\/p>\n\n\n\n

      Clone Issue:<\/strong><\/h4>\n\n\n\n

      Clone Issue means to copy the issue or to create a duplicate of an issue. The main advantage of cloning is that the different teams can work separately, and the issue can be quickly resolved.<\/p>\n\n\n\n

      \"Clone<\/p>\n\n\n\n

      Linking Issue:<\/strong><\/h4>\n\n\n\n

      Linking Issues means creating a relation between two existing issues (either of the same project or different projects). <\/p>\n\n\n\n

      Step 1: Click on the Link available under the More option available on the issue page.<\/p>\n\n\n\n

      \"Access<\/p>\n\n\n\n

      Step 2: Select the issue which you want to link.<\/p>\n\n\n\n

      \"Dropdownlist\"<\/p>\n\n\n\n

      Step 3: Select the issue with whom you want to link.<\/p>\n\n\n\n

      \"Link\"<\/p>\n\n\n\n

      Step 4: Add the comment (optional) and then click on the Link button.<\/p>\n\n\n\n

      \"Issue<\/p>\n\n\n\n

      <\/p>\n","protected":false},"excerpt":{"rendered":"

      JIRA issue is used to track all the work associated with a project. An issue can either be a project task, sub-task, or any other work-related to the project. Steps to create an issue are given below: Step 1: Click on the Create button available on the top menu bar. Step 2: Choose the project […]<\/p>\n","protected":false},"author":1,"featured_media":3703,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[10],"tags":[973,970,972,971],"class_list":["post-3685","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-qa-tutorials","tag-create-issue-in-agile","tag-create-issue-in-jira","tag-plug-ins-in-jira","tag-reate-a-sub-task"],"_links":{"self":[{"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/posts\/3685","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/comments?post=3685"}],"version-history":[{"count":0,"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/posts\/3685\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/media\/3703"}],"wp:attachment":[{"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/media?parent=3685"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/categories?post=3685"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/tags?post=3685"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}