How to categorise items as fillers/low hanging fruit

[Anita Bennett]

We are using a combination of the following fields to give a sense of the nature and complexity of changes.  

• component (standard field)
• theme (custom field)
• estimate (standard field)
• t-shirt size (custom field)

What we are then looking for is something to identify the low hanging fruit .. the low complexity and small items that sit within a component and theme.  We will want to be able to report on them.  Do you have any suggestions?  I am not keen on a label as those cannot get used on kanban, right?  That suggests a field but with one item in the drop-down of "candidate for filler".  Is there another option?

[Marc -Devoteam-]

Hi @Anita Bennett 

You could look at the option to use a Formula field.

https://support.atlassian.com/jira-cloud-administration/docs/create-a-formula-field/ 

[Davit Mkrtchyan - Be On Time]

Hi @Anita Bennett Anita -

It is a great idea to identify those "quick wins". Having a set of low-complexity tasks is a lifesaver for a team when they are waiting for a review or have a small gap between larger items.

Regarding the technical side: labels actually do work on Kanban boards, but you are right to be hesitant. Labels are prone to typos (e.g., "QuickWin" vs "quick-win"), which makes your reporting a nightmare. For reporting, a custom dropdown field (Select List) is definitely the way to go. It ensures data cleanlines and makes your JQL filters reliable.

However, I would like to offer a word of caution from a governance perspective.

There is a common trap called the "Productivity Illusion". It happens when a team starts prioritizing "low hanging fruit" because it feels great to close ten small tickets in a day. The board looks active, the velocity seems high, but the critical, complex tasks - the ones that actually drive the project finish date - remain stuck.

The danger is that "fillers" can easily become a distraction from the critical path.

My suggestion: do not just categorize these items, but limit them. Instead of letting "low hanging fruit" compete for priority with your main goals, treat them as a capacity budget. For example, decide that only 10 percent of the sprint bandwidth can be spent on fillers.

This way, you keep the momentum and the "quick win" feeling, but you ensure that the team's primary energy is spent on the hard, high-value work.

Hope this helps you set up a system that is both easy to report and safe for your delivery!