Description
When a GitHub issue is labeled with the configured trigger label (optio) at creation time, Optio picks it up via the webhook, the agent runs, and a PR is opened. I can see all of this in the issue comments on GitHub. However, the
corresponding task never appears in the Optio UI under Tasks. It's invisible in every state column (queued, working, review, …) even though it's clearly executing in the background.
If I instead create the same GitHub issue without the trigger label, then assign it to Optio from the UI ("Assign to Optio" on an issue), the task shows up correctly in the Tasks section and moves through the pipeline as expected.
The difference between the two flows suggests that webhook-created tasks aren't being stamped with the same ownership/scope metadata that UI-created tasks get. Most likely the workspace id or the creating user. The Tasks list filters those out. The task itself runs fine, it's purely a visibility problem in the UI.
Steps to Reproduce
- Connect GIthub repo
- Create issue in your connected repo
- watch UI
Expected Behavior
A task created via the GitHub webhook (label-triggered) should be visible in the Tasks UI for the user(s) who can see the repo it was created against — the same as a task created by assigning an issue from the UI. The trigger path (webhook vs. UI) should not affect visibility.
Environment
- Optio version: v0.4.0 Helm Chart
- K8s cluster: k3s
- OS: macOS (UI side), Linux/arm64 nodes (cluster side)
Description
When a GitHub issue is labeled with the configured trigger label (optio) at creation time, Optio picks it up via the webhook, the agent runs, and a PR is opened. I can see all of this in the issue comments on GitHub. However, the
corresponding task never appears in the Optio UI under Tasks. It's invisible in every state column (queued, working, review, …) even though it's clearly executing in the background.
If I instead create the same GitHub issue without the trigger label, then assign it to Optio from the UI ("Assign to Optio" on an issue), the task shows up correctly in the Tasks section and moves through the pipeline as expected.
The difference between the two flows suggests that webhook-created tasks aren't being stamped with the same ownership/scope metadata that UI-created tasks get. Most likely the workspace id or the creating user. The Tasks list filters those out. The task itself runs fine, it's purely a visibility problem in the UI.
Steps to Reproduce
Expected Behavior
A task created via the GitHub webhook (label-triggered) should be visible in the Tasks UI for the user(s) who can see the repo it was created against — the same as a task created by assigning an issue from the UI. The trigger path (webhook vs. UI) should not affect visibility.
Environment