Grafana issue detail classifies Task tickets as Bug

[eshulman2]

Summary

The Grafana Forge Issue Detail dashboard reports standalone Jira Task tickets as Bug, even when Langfuse trace metadata correctly contains ticket_type = 'Task'.

Root cause

devtools/grafana/dashboards/forge-issue-detail.json implements the Type panel as a binary Feature/non-Feature test:

SELECT any(if(metadata['ticket_type'] = 'Feature', 1, 0)) as value
FROM default.traces FINAL
WHERE session_id = '${jira_issue}'

The panel maps 1 to Feature and 0 to Bug. Therefore Task, Epic, and any other non-Feature type are displayed as Bug.

This still exists on current main (f4cf630) and is independent of #148 / AISOS-2158: that change improves Langfuse field forwarding and workflow-step labels, but the dashboard discards the actual ticket-type value.

Expected behavior

The Type panel should display the actual non-empty metadata['ticket_type'] value for the selected Jira issue, including at least Feature, Bug, Task, and Epic.

Suggested fix

• Query the ticket type directly (for example, a deterministic latest/any non-empty value) rather than converting it to a boolean.
• Remove the hard-coded 0 -> Bug, 1 -> Feature value mapping.
• Add a dashboard asset test covering Task so the panel cannot regress to a binary mapping.

Acceptance criteria

• A Task trace is displayed as Task in Forge Issue Detail.
• Feature and Bug continue to display correctly.
• Other supported ticket types are not silently classified as Bug.

[ekuris-redhat]

Will be coverd as part of this PR : #123