Mandatory Label field with validation vs. new Issue Types of type sub-task

[Jason_Coomer]

A user has requested that we add 2 new Issue Types of type "sub-task" for his Jira project to more accurately record and distinguish between a "QA" task, and a "Dev" task. They have been using the labels field up till now, but the user in question has advised that other users who create sub-tasks sometimes forget to enter either label.

Would it be better to just make the Labels field mandatory with validation, or create the new Issue Types as requested... or perhaps another approach altogether?

[Grigory Salnikov · Accepted solution]

Hello!

I'd definitely create new Issue Types with possibly different fields. To distinguish between different tasks is the direct function of Issue Types.

[Jason_Coomer]

Thanks Grigory!

[Grigory Salnikov]

You're welcome, @Jason_Coomer :)

Have a nice day!