Work type to use

[Andrea Fernandez]

Hello!
I am doing scrum with my team and using JIRA board to manage our tasks. However, since we are doing a lot of PM work, there are many tasks with dependencies and not purely "do" tasks, more like "get confirmation" or "wait feedback" tasks that we still want to track. I can't figure out the most correct way to visualize this in our board, or which work type should we use, any suggestion?

Thank you!

[Stephen_Lugton · Accepted solution]

Hi @Andrea Fernandez ,

As @Mikael Sandberg said there is no right or wrong work type to use.

There are various ways you can visualise this, including:

• You could create new work item types for each of your task types, e.g.: Task, Feedback, etc., but this may be a bit over complicated
• You can use labels and show them on your board
• You can use Components and show them on your board

For any of these you can create quick filters to only show work items that meet your task type e.g. Labels = "Waiting-on-feedback"

• You could create new statuses in your workflow (and columns on your board) for waiting confirmation, waiting feedback etc.

[Mikael Sandberg · Accepted solution]

Which work type to use is up to you to decide, there is no right or wrong. Instead of creating specific work item types, another option is to use components. Components can be used to break down the space in smaller sections, like in your case in "do" tasks.

[Olga Cheban _TitanApps_]

hi @Andrea Fernandez ! welcome to the Community!

Those "get confirmation" and "wait for feedback" steps sound less like standalone tasks and more like checkpoints that belong inside a parent work item. Creating separate tickets for them tends to clutter the board and inflate your sprint count without giving you a clearer picture.

A simpler way to handle this is with checklists. You can keep one work item for the actual deliverable and track all the smaller dependencies, approvals, and waiting states as checklist items inside it. Our app, Smart Checklist for Jira, is built exactly for this. A few features that might help in your case:

• Custom statuses on each item, so "Waiting for confirmation" or "Pending feedback" become visible states, not separate tickets.
• Tagging people per item, so each dependency has a clear owner.
• Adding deadlines, links, and extra details in expandable sections for checklist items
• A progress bar on the parent work item, so you can see at a glance how close it is to Done
• Reusable templates, so recurring PM checklists (kickoffs, approvals, releases) can be applied to new work items in one click or even automatically

This way, your board stays focused on real deliverables, and the waiting/coordination steps stay tracked where they belong.

Here is an example - a release readiness checklist that is organized with headers grouping exact steps for each team. Let me know if you have any questions!