JIRA is now available as three separate applications, JIRA Software, JIRA Service Desk, and JIRA Core. For more information on administering these applications, refer to the Administering JIRA Applications documentation.

Defining Issue Type Field Values

JIRA ships with a set of default 'issue types' to help you get started. Everyone's needs are different and so JIRA also allows you to add, edit and delete your own custom issue types. The diagram on Configuring Fields and Screens shows how issue types relate to other entities in JIRA.

Note that you can also:

Tip: You can quickly configure the workflow/screen design of an existing issue type for a project via the project administration page. See Defining a Project for details.

On this page:

Creating an issue type

When creating a new issue type in JIRA, you can create either a new standard or sub-task issue type. However, to create a sub-task issue type, you must Enable sub-tasks.

You can also create sub-tasks on the Sub-Tasks page. See Creating a sub-task issue type for details.

To create a new issue type:

  1. Log in as a user with the JIRA Administrators global permission.
  2. Choose > Issues. Select Issue Types to open the Issue Types page, which lists all issue types.
    (tick)  Keyboard shortcut: g + g + start typing issue types
  3. Click the Add Issue Type button and enter the following details:
    • Name — enter a short phrase that best describes your new issue type.
    • Description — enter a sentence or two to describe when this issue type should be used.
    • Type — specify whether the issue type you are creating is a Standard issue type or a Sub-Task issue type. Sub-tasks are associated with individual Standard issues.
      (info) This option will not be available if sub-tasks are disabled.
  4. Click the Add button to create your new issue type.
    (info) Your new issue type will be automatically added to the Default Issue Type Scheme. You may want to also add it to other issue type schemes — for more information, see Managing Issue Type Schemes.

Deleting an issue type

(warning) Before you begin:

  • If any issues of the Issue Type you are about to delete exist in your JIRA installation, please ensure this Issue Type has the following requirements (to ensure JIRA prompts you to choose a new Issue Type for those issues):
  • Alternatively, you can simply search for all issues that currently use the Issue Type which you are about to delete and perform a Bulk Move to change those issues to a different Issue Type.

To delete an Issue Type:

  1. Log in as a user with the JIRA Administrators global permission.
  2. Choose > Issues. Select Issue Types to open the Issue Types page, which lists all issue types.
    (tick) Keyboard shortcut: g + g + start typing issue types
  3. Click the Delete link (in the Operations column) for the issue type that you wish to delete.
  4. Complete the fields

Editing an issue type

To change the name, description or icon for an issue type:

  1. Log in as a user with the JIRA Administrators global permission.
  2. Choose > Issues. Select Issue Types to open the Issue Types page, which lists all issue types.
    (tick) Keyboard shortcut: g + g + start typing issue types
  3. Click the Edit link (in the Operations column) for the issue type that you wish to edit.
  4. Edit the Name, Description and/or Icon as described above for Creating an issue type.

(info) Please Note: To reorder an Issue Type, or set it as a default, see Associating Issue Types with Projects. (Reordering issue types changes the order in which they are displayed to the user who is creating an issue; and the default issue type is the one that is displayed in the selection-box — see Creating an Issue.)

Was this helpful?

Thanks for your feedback!

Why was this unhelpful?

18 Archived comments

  1. User avatar

    Robert Gosselin

    Is there a way to define a bug as a sub-task?

    Reason we want to do this is to track bugs found while working on a task or user story and keep those together in Greenhopper.

    Also need to know If the find/fix reports would still work if we define a bug as a sub-task? 

    13 Dec 2012
  2. User avatar


    I'd like to modify the field 'Issue Type' to a cascading select type. Any idea how to do this?


    17 Dec 2012
  3. User avatar


    It seems only the issue type "Story" has the field "Story Points," but the description says only Greenhopper adds those.  So what is the workflow?  I simply want to add a requirement, bug, etc., put it in a sprint, and assign story points and sub-tasks.  How do I accomplish this??

    04 Apr 2013
  4. User avatar


    When you create a sub task issue type, can tu associate a particular workflow to it?

    13 May 2013
    1. User avatar

      Ian D

      Yes. Same as with parent tasks.  

      26 Jul 2013
  5. User avatar

    Aissa Brahimi


    I would like to change a issue type icon.
    Can you help?

    15 Jan 2014
    1. User avatar



      That's simple. Just follow the following steps:

      1. Log in as Jira administrator
      2. Go to Issues -> Issue types
      3. Locate the Issue type of which you want to change the Icon and click Edit on the right
      4. Insert the Icon URL or click Select image

      Good luck!

      15 Feb 2014
  6. User avatar


    I would like to be able to edit the issue type so that I can change it from a "Story" to an "Order".  Any idea how I do this after an issue has already been created?

    18 Feb 2014
    1. User avatar

      Christine Burwinkle

      Hi there, you should be able to use the Edit button to do this (as long as you have the correct permissions). See Editing an Issue.

      Cheers, Christine

      20 Feb 2014
  7. User avatar

    Tim Yeung

    I am having a problem when updating the description of an issue type.

    Below is what I have tried:

    1. In http://<JIRA>/secure/admin/ViewIssueTypes.jspa
      1. Edit "Bug" description; e.g. set it to "xxx"
      2. The description on "ViewIssueTypes" is updated to "xxx"
    2. But in the local help, http://<JIRA>/secure/ShowConstantsHelp.jspa?decorator=popup#IssueTypes
      1. The description does not show "xxx", instead it shows the default? description "A problem which impairs or prevents the functions of the product."

    It seems this behavior only happens in native JIRA issue types, e.g. if I edit a non native JIRA issue type, the description displays correctly.

    Is this a bug or I am doing something wrong? Thanks.


    02 Sep 2014
    1. User avatar

      Evangelos Vrocharis

      Hi Tim,

      I just noticed the same thing on my production instance today. The description for the issue type Story on my instance is blank on the help page and the view page in the admin section of the projects even though there is a text for it. Updating the text makes no difference.

      Interestingly enough, a test instance with the same data is not having this issue although we did upgrade to 6.3.10 there the other day. Looks like some kind of strange glitch/bug here, I will report back in a couple of days after we upgrade our production instance if it went away.

      17 Nov 2014
  8. User avatar

    Alex Kuhner

    Hi - Is it possible to have Story Points on things other than Stories?  Technical Debt is a story, it takes effort, the team sized it in the same way they size User Stories, and it counts towards/against velocity in the same way, so we need to account for it in the same way.  I can't figure out how to make an Issue Type which I can call "Technical Debt" but have it treated the same as a Story - is that possible?  Will it ever be possible?  I'd rather not just treat Technical Debt as a Story, it's important to make the buildup of debt as visible as possible.

    We are on JIRA v6.3.4a with JIRA Agile v6.6.0


    06 Oct 2014
    1. User avatar

      Warren Thompson

      Hi Alex,

      Yes it is possible, what you need to do is assign your new issue type to the custom field Story Points.

      Basically, story points are a custom number field, and in a default setting are only available on the epic and story issue types. If you have admin access, you need to select issue from your admin drop-down (the cog icon), then select Custom Fields in the left column. Scroll down until you see Story Points, and then add your new issue type, tech debt. That'll make the story point field available for that issue type.

      Hope that helps!


      07 Oct 2014
      1. User avatar

        Alex Kuhner

        That's great, thanks!  I fixed that and re-indexed.  Now that I've done that, JIRA will count those Story Points in Velocity and reports like that, correct?

        I'm trying to figure out why our setup includes another Custom Field just called "Points," which does not look like a JIRA managed field (mostly because it says it's a text field instead of a number field.  That's not a JIRA thing, right?


        07 Oct 2014
        1. User avatar

          Warren Thompson

          Hi Alex,

          Yep, the story points should be counted towards your velocity and reports. You can create a test project if you like to try it out.

          I haven't heard of the Points custom field, it's not in the default setting as far as I can see. It may have been created by another admin at some time? It may have been to try and add points in another way, that weren't linked to the reports? But I'm just guessing here...

          Hope that helps,


          07 Oct 2014
  9. User avatar

    Blaine Simpson

    With default settings for a Scrum project, it seems that the only place I can change Estimate/Story Point values (for Stories) is the Detail view under Backlog or Active Sprints screens.  Since one can not display the Detail view of Epics from these screens, it seems to be impossible to assign Estimate/Story Point values for Epics.  The Story Point field is explicitly set (by default) to apply to Epics.  Is there any way to actually use the field for Epics without customizing field or screen settings?

    18 Apr 2015
  10. User avatar

    Peter Sveistrup

    The blue cog icon is missing in the article.

    11 Jun 2015
  11. User avatar

    Xiao Clark

    As a user, where can I find the descriptions that are added to our ticket types during the above process?

    25 Jun 2015
Powered by Confluence and Scroll Viewport