Task workflows are identified in Grafana as Bug type instead of Task

[ekuris-redhat]

Problem

Task takeover workflows are labeled as Bug type in Langfuse/Grafana dashboards instead of Task. This makes it impossible to filter and attribute metrics (token costs, latency, generation counts) to the correct workflow type in dashboards.

Expected Behavior

Task takeover workflows should be tagged with their actual Jira issue type (Task) in Langfuse traces, so Grafana dashboards correctly distinguish them from Bug and Feature workflows.

Impact

Grafana views based on ticket_type tags misattribute Task workflow metrics to the Bug category, leading to inaccurate cost and performance reporting per workflow type.

[eshulman2]

Duplicates