Understanding issue types in jira

[Kevin Gillooly]

Is the use of Issue Type in Jira Cloud different that their us in DC or Server?

[Rajesh Viswanathan]

Issue types distinguish different types of work in unique ways, and help you identify, categorize, and report on your team’s work across your Jira site. They can help your team build more structure into your working process. 

[chloe Tonge]

Hi @Christina Nelson really useful. The hierarchy of issues (diagram) in particular. Can you help me understand where an assets sits within the diagram. thanks

[Rajesh Viswanathan]

wonderful article to start with Jira

[Milos Ristic]

Really interesting. I like really to play the games with the computer. It's enormously fun. :)

[Danine O_Donnell]

hey all - I found an article once on the meanings of the drop down icons...meaning of blue/red boxes etc/ Anyone here knows what I am referring to? 

[Prerna Sony]

Thanks! Informative and useful article !

[Dyrell Charvin Kenn Canono]

Very concise and easy to digest. Thanks a lot!

[Michele Stein]

Last company where I worked, our issues were grouped into 

--- Epics

--- --- Features

--- --- --- Stories

--- --- --- --- Tasks (equivalent to subtasks in article above)

With each line being a sub-category of the line above.  However I'm not seeing the option of a level between Stories and Epics in this current software.  Can the extra level be added somehow?

[Rajesh Viswanathan]

excellent 

[Jinav Shah]

Also, in our organisation - we have created additional issue types for specific type of work. Like Task brief, documentation etc. 

While we want everything as user story - sometimes having this additional issue type helps us accomodate one thing in a sprint cycle.

[Ashish Agarwal]

Good one to understand for a newbee. Easy to understand. Thanks

[Dragos M]

Great article with clear explanations and structured approach, very easy to understand the basics. Thanks @Christina Nelson 

[Jonas Flodqvist]

Great post by @Adam Sterrie and his analogy example of putting up shelves.
As he wrote (..putting up the actual shelf is the story/improvement/new feature.)
The shelf can have several planes/boards and you then make each shelf like a story. Several shelves can then be placed in an Epic...that's how you get that concept.

Because we work agile and learn as we do the same things, the job can be done faster and with less (sloppy work) / bugs.
(And another example if when we have a nice velocity and we do continue to do a super job...we get a fresh (developer - carpenter)...with previous knowlige of the shelf/ wall...and bugs...will apper again.

And maybe we we have a tester with a test task...verifying if we can place a book on the shelf. (Can it stand the weight - is the shelf leveled).
Stated in the test criteria (DoD).

Again, super nice analogy, thanx. :o)

[Nayeemuddin Khan]

@Christina Nelson , when will Atlassian facilitate 3 or multilayered Issues hierarchy structure? any idea, or any suggestion to create multi layered Issue hierarchy?

thanks,

Nayeem