Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,456,341
Community Members
 
Community Events
176
Community Groups

How to explain Issue Types?

Edited

Issue Types are easy to understand, but not so easy to explain.

I usally use examples like "Booking Room" and "Feature" and explain in a longer run the differences in workflow and needed informations - screens.

 

The most short explaination I found: Issue Types are types of processes.

But does that fit? Does it explain the whole meaning of Issue Types?

2 comments

I tend to use "Issue types are an indication of the most defining kind of information you hold to want to hold about an issue".  Not "important", but "defining".  This is because the issue type can be used to define how an issue behaves.

Think of the difference between using a single issue type of "Pet" and several that are "dog", "cat", "bunny", "horse", "fish" and "snake".  They all have a lot in common - a need for food and shelter, and they're all companions of some sort for a human.  But they have different characteristic (fields), different needs (more like attributes that you need to take care of) and, let's say you're tracking a day in the life of your pet as a Jira issue, then a different workflow. 

The dog needs a workflow that includes sleeping, being fed morning, being walked, some fuss, being fed evening, but the cat needs status like sleeping, food bowl refill (not necessarily eating, just a refill), nap 1, wander round garden, nap 2, do something to annoy the humans, and so-on.

There are better analogies, but I like my cat, and want a dog.

So, you hang all those things off what the "issue type" is.

Like # people like this

Hi @Stephan Hannach ,

In addition to Nic's excellent comment above, you may find this documentation helpful.

Like # people like this

Comment

Log in or Sign up to comment
TAGS

Atlassian Community Events