Issue filters in Unassigned Work in Workload Balancer | Community
Skip to main content
tibormolnar
tibormolnar
Level 4
March 26, 2025
Solved

Issue filters in Unassigned Work in Workload Balancer

  • March 26, 2025
  • 1 reply
  • 388 views

Hi All,

in WLB, under settings, we have the option to "Include hours from issues". If this is checked, issues with non-zero planned hours & duration are displayed, both in the "Unassigned Work" and "Assigned Work" sections. - This is great.

 

I need to filter down the displayed items on Issues only, with a specific value in a custom field.

I can do this easily in the Assigned Work section, because in the filter section I can use Issue fields as filter:

In the "Unassigned Work" section, the option to filter on issue fields seems to be missing:

Is it just me overseeing something, or this filtering option really doesn't exist?

Can anyone think of a workaround?

Thank you,

Tibor

 

Best answer by Doug_Den_Hoed__AtAppStore

 

Hi @tibormolnar,

 

Interesting observation, and one I'd not noticed. I don't recall any secret levers to "turn on" WLB Unassigned Issue filtering, so suspect it is an oversight that you might want to consider raising as an Idea (citing, repeating, or asking to move this item for reference).

 

Since WLB Unassigned Task filtering is currently available, one workaround could be to create one or more "Issue Bucket" projects, and change your procedure (whether manually, or via some automation) to convert such non-zero hour unassigned issues into Tasks within those Projects (whether auto-deleting the Issue for simplicity, or preserving it for consistency). Admittedly, that's a hack...but it would accomplish your immediate requirement, and could provide additional native advantages (e.g. Gantt visualization, ability to add predecessors between such "Issue Tasks", ability to create parent tasks for organizational and scheduling purposes an drag and drop them for prioritization, etc.).

 

Beyond just native Workfront functionality, I also invite you to consider our Resource Grid solution, which -- being based upon the Assignment object -- does support filtering for both Tasks and Issues, equally. I'd be happy to chat further at doug.denhoed@atappstore.com for more information, too.

 

Regards,

Doug

1 reply

Doug_Den_Hoed__AtAppStore
Community Advisor
Doug_Den_Hoed__AtAppStoreCommunity AdvisorAccepted solution
Community Advisor
March 26, 2025

 

Hi @tibormolnar,

 

Interesting observation, and one I'd not noticed. I don't recall any secret levers to "turn on" WLB Unassigned Issue filtering, so suspect it is an oversight that you might want to consider raising as an Idea (citing, repeating, or asking to move this item for reference).

 

Since WLB Unassigned Task filtering is currently available, one workaround could be to create one or more "Issue Bucket" projects, and change your procedure (whether manually, or via some automation) to convert such non-zero hour unassigned issues into Tasks within those Projects (whether auto-deleting the Issue for simplicity, or preserving it for consistency). Admittedly, that's a hack...but it would accomplish your immediate requirement, and could provide additional native advantages (e.g. Gantt visualization, ability to add predecessors between such "Issue Tasks", ability to create parent tasks for organizational and scheduling purposes an drag and drop them for prioritization, etc.).

 

Beyond just native Workfront functionality, I also invite you to consider our Resource Grid solution, which -- being based upon the Assignment object -- does support filtering for both Tasks and Issues, equally. I'd be happy to chat further at doug.denhoed@atappstore.com for more information, too.

 

Regards,

Doug

tibormolnar
tibormolnarAuthor
Level 4
March 27, 2025

Thanks for the confirmation, Doug. I'll raise this with Adobe.

The suggested workaround makes sence but I can't apply that in our scenario. I need to keep issues as issues.

Terms & ConditionsAccessibility statement

Loading footer...