[{"data":1,"prerenderedAt":226},["ShallowReactive",2],{"post-\u002Fblog\u002F2018\u002Fcreating-custom-issue-types-in-jira":3},{"id":4,"title":5,"body":6,"categories":205,"date":209,"description":210,"extension":211,"image":54,"meta":212,"navigation":213,"path":214,"seo":215,"stem":216,"tags":217,"__hash__":225},"blog\u002Fblog\u002F2018\u002Fcreating-custom-issue-types-in-jira.md","Creating Custom Issue Types for JIRA",{"type":7,"value":8,"toc":196},"minimark",[9,14,18,22,29,32,35,41,49,55,62,68,75,81,87,98,104,119,125,136,142,145,149,155,171,175,178,181,185],[10,11,13],"h2",{"id":12},"introduction","Introduction",[15,16,17],"p",{},"Custom issue types are one of the most powerful features of Jira. Since issues\ncan be queried and linked with other issues, Confluence pages or anything else\nthat can have a URL, you can use them for many different purposes that usually\nrequire a separate tool. Examples are impediments and requirements. Impediments\nwill move to the Scrum Master's backlog; requirements tend to link to user\nstories that try to satisfy that single requirement.",[10,19,21],{"id":20},"creating-a-custom-issue-type","Creating a Custom Issue Type",[15,23,24],{},[25,26],"img",{"alt":27,"src":28},"Jira project settings navigation","\u002Fimages\u002Fblog\u002F2018\u002F08\u002Fimage-2.png",[15,30,31],{},"To create a custom issue type for a project, you first need to get into the\nproject settings (click the bottom left corner of the project page).",[15,33,34],{},"A part of the settings page shows the issue types already present in this project.",[15,36,37],{},[25,38],{"alt":39,"src":40},"Jira issue types in project settings","\u002Fimages\u002Fblog\u002F2018\u002F08\u002Fimage-3.png",[15,42,43,44,48],{},"If you click on the ",[45,46,47],"strong",{},"Issue types"," menu item in the left menu, you get a more\ndetailed overview of the types:",[15,50,51],{},[25,52],{"alt":53,"src":54},"Jira issue types overview","\u002Fimages\u002Fblog\u002F2018\u002F08\u002Fimage-4.png",[15,56,57,58,61],{},"The ",[45,59,60],{},"Actions"," button in the top right corner is what you need. On the next\nscreen you can pull in issue types you have already defined into the current\nproject.",[15,63,64],{},[25,65],{"alt":66,"src":67},"Jira add issue type to scheme","\u002Fimages\u002Fblog\u002F2018\u002F08\u002Fimage-5.png",[15,69,70,71,74],{},"If the issue type is not yet defined, you can create one with the ",[45,72,73],{},"Add issue\ntype"," button in the top right corner.",[15,76,77],{},[25,78],{"alt":79,"src":80},"Jira define new issue type","\u002Fimages\u002Fblog\u002F2018\u002F08\u002Fimage-7.png",[15,82,83],{},[25,84],{"alt":85,"src":86},"Jira new issue type form","\u002Fimages\u002Fblog\u002F2018\u002F08\u002Fimage-8.png",[15,88,89,90,93,94,97],{},"When you have defined your new issue type, reload the page to make it appear in\nthe ",[45,91,92],{},"Available issue types"," column. Now you can move it over to the ",[45,95,96],{},"Issue\nTypes for Current Scheme"," column.",[15,99,100],{},[25,101],{"alt":102,"src":103},"Jira move issue type to scheme","\u002Fimages\u002Fblog\u002F2018\u002F08\u002Fimage-9.png",[15,105,106,107,110,111,114,115,118],{},"Now click ",[45,108,109],{},"Save",". If you don't like the icon of the new issue type, go to the\nglobal ",[45,112,113],{},"Issue"," settings of Jira, find your new type in the list and click\n",[45,116,117],{},"Edit",".",[15,120,121],{},[25,122],{"alt":123,"src":124},"Jira global issue type edit","\u002Fimages\u002Fblog\u002F2018\u002F08\u002Fimage-10.png",[15,126,127,128,131,132,135],{},"You can now click ",[45,129,130],{},"Select image"," to change the icon and then click ",[45,133,134],{},"Update","\nto save the changes.",[15,137,138],{},[25,139],{"alt":140,"src":141},"Jira issue type icon selection","\u002Fimages\u002Fblog\u002F2018\u002F08\u002Fimage-11.png",[15,143,144],{},"After this, creating a new requirement is straightforward. You can use filters\nto find requirements that are not yet addressed by any task, story, or test.",[10,146,148],{"id":147},"query-requirements-with-jql","Query Requirements with JQL",[15,150,151],{},[25,152],{"alt":153,"src":154},"Jira JQL filter for requirements without links","\u002Fimages\u002Fblog\u002F2018\u002F08\u002Fimage-12.png",[15,156,157,158,165,166,170],{},"If you want to show only requirements without links, you need a plugin. I\nrecommend the ",[159,160,164],"a",{"href":161,"rel":162},"https:\u002F\u002Fmarketplace.atlassian.com\u002Fapps\u002F6820\u002Fscriptrunner-for-jira",[163],"nofollow","Script Runner Plugin","\nfrom Adaptavist. It provides the JQL function ",[167,168,169],"code",{},"hasLinks()"," to filter issues\nbased on their links.",[10,172,174],{"id":173},"issue-type-workflow","Issue Type Workflow",[15,176,177],{},"For some issue types it makes sense to assign a custom workflow. Requirements,\nfor example, are never simply \"Done\". They typically start in a draft or\ndocumentation phase, go through a review (by management, customers, or users)\nand then enter a demand state. Once a requirement has been satisfied — e.g.\nthrough implementation and automated testing — it transitions to an active\nstate where those tests continuously verify it stays satisfied.",[15,179,180],{},"How to define a custom workflow will be covered in a separate post.",[10,182,184],{"id":183},"further-reading","Further Reading",[186,187,188],"ul",{},[189,190,191],"li",{},[159,192,195],{"href":193,"rel":194},"https:\u002F\u002Fconfluence.atlassian.com\u002Fadminjiracloud\u002Fadding-editing-and-deleting-an-issue-type-844500747.html",[163],"Adding, editing and deleting an issue type – Jira Cloud",{"title":197,"searchDepth":198,"depth":198,"links":199},"",2,[200,201,202,203,204],{"id":12,"depth":198,"text":13},{"id":20,"depth":198,"text":21},{"id":147,"depth":198,"text":148},{"id":173,"depth":198,"text":174},{"id":183,"depth":198,"text":184},[206,207,208],"Atlassian","JIRA","Tools","2018-08-19","Custom issue types are one of Jira's most powerful features. Learn how to create and configure them for requirements, impediments, and other use cases that usually require a separate tool.\n","md",{},true,"\u002Fblog\u002F2018\u002Fcreating-custom-issue-types-in-jira",{"title":5,"description":210},"blog\u002F2018\u002Fcreating-custom-issue-types-in-jira",[218,219,220,221,222,223,224],"atlassian","jira","issue-types","workflow","agile","scrum","requirements","_56wKTkvJnyi4KvOp0T_soeFUTTPBDaasHEU-6PmElk",1778331519480]