A task is linked to the issue it came from, and that issue keeps gathering context as people comment on it. The Issue tab shows that conversation, and while a run is still working you can feed new comments into it with Apply comments. This page covers both. For where the link comes from, see Where tasks come from.
The Issue tab
On a task that came from an issue, the task’s detail page has two tabs — Overview and Issue. (The Issue tab only appears when the task has a linked issue.) Open Issue to see:
- The issue’s description — the body of the GitHub or Jira issue, as written.
- Comments (N) — every comment on the issue, each with its author, date, and text. When there are none, it reads “No comments on this issue yet.”
- A link in the header that opens the original issue in GitHub or Jira.
The comments sync in automatically from your project-management tool — you don’t write them in DIJJI.ai. Comment on the issue in GitHub or Jira the way you normally would, and the comments appear here shortly after. (A task with no linked issue — a system task — has no Issue tab.)
To see what a task’s work cost, open one of its runs: the run’s detail page has a Cost so far panel. Spend also rolls up into the project’s Reports.
Apply comments to a working run
When new comments arrive after a run has already started, you can hand them to the run in progress instead of starting over. While a run is in flight — Pending, Queued, or Running — and at least one comment has arrived since DIJJI.ai last looked, an Apply comments button appears in the action bar on the task’s Overview.
Select it, and the run folds the new comments into what it’s doing, picking up the added guidance on the same attempt. The button clears once there’s nothing new left to apply.
Why only while it’s working
Apply comments is offered only for an in-flight run, by design:
- A run that’s still working is on a live branch that hasn’t merged yet, so new context can steer it safely.
- A finished task — Completed, Failed, or Cancelled — has already had its say; its work has shipped or stopped, so it’s left untouched.
To act on new comments for a task that has already finished, start a fresh attempt instead — see Retry a failed run or Execute a task. The new run reads the issue and its comments from the start.