Is there a way to have a request queue create tasks only (no issues)? | Community
Skip to main content
M
megkart
Level 2
March 30, 2026
Solved

Is there a way to have a request queue create tasks only (no issues)?

  • March 30, 2026
  • 3 replies
  • 89 views

We're currently using a request queue that creates issues by default. Our team then works with tasks, so we end up with both issues and tasks in our projects. This is causing confusion.

Ideally, we'd like requests to come in as tasks only — no issues at all. We want to keep things simple and have one object type for the team to work from.

I know routing rules can auto-convert issues to tasks, but the original issue still remains. Is there a way to either:

  1. Have the request queue create tasks directly, skipping issues entirely?
  1. Or is there another approach anyone has found that achieves a "tasks only" experience?
Best answer by AutumnE

Hi, ​@megkart 

Workfront request queues always create issues — it’s not possible to create tasks directly from a request or skip the issue object.

The usual approaches are:

  • Auto-convert issues to tasks and have teams work only from task reports/views

  • Or, if you truly want a tasks-only model, use Workfront Fusion to convert the issue to a task and then delete the original issue

There is no native, UI-only way to eliminate issues entirely from the request process.

Here are a few options I’ve implemented for clients:

 

  1. Auto‑convert + hide issues operationally
    1. This is the closest you can get without custom automation.
    2. Steps:
      1. Requests go into a queue
      2. Routing rules immediately convert them to tasks in the correct project
      3. Team members:
        • Work only from task reports, task lists, or project views
        • Never interact with the queue or issues area

Recommended setup

  • Lock down issue access for team members (Remove “View Issues” if possible)
  • Create:
    • “My Work (Tasks)” reports
    • Project task views only
  • Train requestors + team that:
    • Issues are intake only. All real work happens in tasks.

Issues technically still exist (but are invisible day-to-day)

  1. Auto‑convert AND auto‑delete the issue (via Fusion)

Using Workfront Fusion:

  1. Trigger on: New Issue created

  2. Convert Issue → Task

  3. Capture the new Task ID

  4. Delete the original Issue

3 replies

AutumnE
Adobe Champion
AutumnEAdobe ChampionAccepted solution
Adobe Champion
March 30, 2026

Hi, ​@megkart 

Workfront request queues always create issues — it’s not possible to create tasks directly from a request or skip the issue object.

The usual approaches are:

  • Auto-convert issues to tasks and have teams work only from task reports/views

  • Or, if you truly want a tasks-only model, use Workfront Fusion to convert the issue to a task and then delete the original issue

There is no native, UI-only way to eliminate issues entirely from the request process.

Here are a few options I’ve implemented for clients:

 

  1. Auto‑convert + hide issues operationally
    1. This is the closest you can get without custom automation.
    2. Steps:
      1. Requests go into a queue
      2. Routing rules immediately convert them to tasks in the correct project
      3. Team members:
        • Work only from task reports, task lists, or project views
        • Never interact with the queue or issues area

Recommended setup

  • Lock down issue access for team members (Remove “View Issues” if possible)
  • Create:
    • “My Work (Tasks)” reports
    • Project task views only
  • Train requestors + team that:
    • Issues are intake only. All real work happens in tasks.

Issues technically still exist (but are invisible day-to-day)

  1. Auto‑convert AND auto‑delete the issue (via Fusion)

Using Workfront Fusion:

  1. Trigger on: New Issue created

  2. Convert Issue → Task

  3. Capture the new Task ID

  4. Delete the original Issue

Autumn Earle
    J
    JD_FCFS
    June 1, 2026

    Hey ​@AutumnE , sorry to bug ya, but do you happen to know where I can find documentation on routing rules automatically converting Issues to Tasks?


    I think the non-fusion workflow above  will actually work great for us but I’m not seeing the option in queue setup.

      J
      JD_FCFS
      May 27, 2026

      I’m not seeing the option to automatically convert Issues to Tasks from Routing Rules - am I missing something?  Routing to another project just creates an Issue somewhere else.

      U
      user01245
      Level 3
      May 27, 2026

      I’d love it if this were possible, or, even better for my use case would be if request queues could create projects. As it is now we end up with duplicates issues/request, projects and tasks. The thing people have the hardest time with in Workfront is the different object types, and I wish they had built it around one object type that could be used multiple ways. Obviously it’s too late to change that, but it’s one of the things I like least about the system.  

        Terms & ConditionsAccessibility statement

        Loading footer...