difference b/w default issues ? why we use default issues types ? where we use default issue types?

[Arjun]

difference b/w default issues ? why we use default issues types ? where we use default issue types? 

please give me detailed information. 

[Nic Brough -Adaptavist-]

Actually, where and when you use them is up to you.  What matches your process?  If you don't want to use "tasks", don't use them.

Assuming you have Jira Software, then you have three groups of types to think about:

• Epic: only one issue type can take this type, and it is strongly recommended that you do not rename it
• Issues: you can create or remove issue types that are issue level as you need.  Most of us do make use of Story, Bug and several of the others that Jira creates by default, but we do drop them from projects that don't need them, and add our own issue types
• Sub-tasks: pretty much the same as issue types - you can add and remove anything you want (but in Team-managed-projects, you only get one "sub-task" at the moment, not a variable list)

[Fazila Ashraf]

Hi Srinivas

Default issue types are the ones that comes bundled with the JIRA installation. Atlassian has setup the default issue types as the standards that are specific to the product installs.

Most probably you would want to start with those issue types and then extend with custom ones as per your requirements. 

[Arjun]

Hi Fazila

Thank you for your response.

yeah the are 7 default issue types , but my equation is  where we use those default issue types ? When we use those default issue types ? And difference b/w those default issue types.. I need some detailed clarification.

thank you

[Fazila Ashraf]

Ah.. i hope the information in https://confluence.atlassian.com/adminjiraserver/issue-fields-and-statuses-938847116.html helps you on that..