Repository navigation
Conversation
feat(jira): sync assigned issues into project tasks
fix(board): track agent questions and completion accurately
fix(conversations): default Codex model to GPT 6 Sol
fix(tasks): show done tasks in archived list
feat(tasks): mark Jira-linked board cards
feat(tasks): attach images to initial ticket descriptions
Contributor
 [High impact] The changes span project work, Jira imports, and shared agent status flows. Fix saved manual moves before merging; they can hide an agent's current work on later turns. FindingsFix with agent prompt### Issue 1
apps/emdash-desktop/src/core/features/projects/browser/stores/project-view.ts:46-48
Move a working task to Review, let the agent finish, then send another prompt. When the conversation returns to `working`, its key matches the old saved override. The card stays in Review instead of Running because the mismatched override was never removed.
Remove the saved override when the observed key first changes, and test a full status cycle.
### Issue 2
apps/emdash-desktop/src/core/features/projects/browser/components/task-view/task-board.tsx:108-112
Cards can only move through mouse dragging. The card's button opens the task, and there is no keyboard action for choosing another column. Add a keyboard-accessible move menu or equivalent controls so keyboard users can start backlog work and archive cards from the board.
Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
---
For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.SummaryThis PR adds a project task board, Jira issue imports, and richer agent status hooks.
Diagram%%{init: {'theme': 'neutral'}}%%
flowchart LR
Jira[Jira query and comments] --> Sync[Import or refresh task]
Sync --> Task[Saved task]
Hooks[Agent hooks] --> Status[Conversation status]
Task --> Board[Project board]
Status --> Board
PR[Pull request status] --> Board
Board -->|Backlog to Running| Agent[Create and start conversation]
Board -->|Drop on Done| Confirm[Confirm archive]
Reviews (1) · Last reviewed commit: "feat(board): enable task card drag and d..." · Reviewed by Greptile |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
Comment on lines
+46
to
+48
| boardOverride(taskId: string, agentStatusKey: string): BoardColumn | undefined { | ||
| const override = this.handle.value.boardOverrides?.[taskId]; | ||
| return override?.agentStatusKey === agentStatusKey ? override.column : undefined; |
Contributor
There was a problem hiding this comment.
Move a working task to Review, let the agent finish, then send another prompt. When the conversation returns to working, its key matches the old saved override. The card stays in Review instead of Running because the mismatched override was never removed.
Remove the saved override when the observed key first changes, and test a full status cycle.
Prompt To Fix With AI
This is a comment left during a code review.
Path: apps/emdash-desktop/src/core/features/projects/browser/stores/project-view.ts
Line: 46-48
Comment:
**Expired moves return**
Move a working task to Review, let the agent finish, then send another prompt. When the conversation returns to `working`, its key matches the old saved override. The card stays in Review instead of Running because the mismatched override was never removed.
Remove the saved override when the observed key first changes, and test a full status cycle.
---
For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.
Comment on lines
+108
to
+112
| <li className="shrink-0" draggable onDragStart={(event) => onDragStart(event, taskId)}> | ||
| <Button | ||
| variant="secondary" | ||
| disabled={opening} | ||
| onClick={() => void open()} |
Contributor
There was a problem hiding this comment.
Cards can only move through mouse dragging. The card's button opens the task, and there is no keyboard action for choosing another column. Add a keyboard-accessible move menu or equivalent controls so keyboard users can start backlog work and archive cards from the board.
Prompt To Fix With AI
This is a comment left during a code review.
Path: apps/emdash-desktop/src/core/features/projects/browser/components/task-view/task-board.tsx
Line: 108-112
Comment:
**Keyboard users cannot move cards**
Cards can only move through mouse dragging. The card's button opens the task, and there is no keyboard action for choosing another column. Add a keyboard-accessible move menu or equivalent controls so keyboard users can start backlog work and archive cards from the board.
---
For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Give a short summary of what changed, why it's needed, and any important implementation notes.
Related issues
Link related issues. If this PR fixes an issue, mention it like: Fixes #123.
Testing
List the checks you ran, for example
pnpm run format,pnpm run lint,pnpm run typecheck,pnpm run test, and any manual testing.Screenshot/Recording (if applicable)
Attach a screenshot, GIF, or recording of the change. This is optional, but helps reviewers
understand UI or workflow changes.
Checklist
messages and, when possible, the PR title