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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


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
Community Members
Community Events
Community Groups

To clasify process, what do you prefer? Lots of issuetypes or lots of customfields?

laralg Rising Star Mar 06, 2019


Recently I am working for a new Jira that needs a lot of kanban projects, each project/team its different and they have their own way of doing things.

They have provided status for their boards and some fields to clasify their issues. But I am not sure what is better for them. Different issuetypes for each field, of a single issuetype with a select list to clasify them.

Important, these fields are for different process.

PRO issuetypes:
You select what you want the moment you open the issue, the screen can depend on the issuetype, and the workflow.

PRO customfields.

A select list is more clean, you have one issuetype for everything and then a  single select list for each project where they can choose what that issues is going to be about.

I love to hear how you make kanban for different teams, specially not IT, and how do you make them clasify their issues.

Do you use a single Task and then clasify or a issuetype that is more familiar to them?

1 comment

I would say don't rely on just custom fields or issue types. Have a balance of both.

Creating too many custom fields can impact the performance. Create common Issue Types doing similar things with similar custom fields. Use custom field contexts and field configurations to optimise the usage of the custom fields. Two Issue types can have same screen with same set of custom fields but based on field configuration you can hide some fields.

Issue types give clarity for the end user in selecting the type of issue they are raising. Having just one issue type can be confusing.


Log in or Sign up to comment