[Tracking] Task details and Tasks page usability

Open
  • Is something wrong?
#427 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
28/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
csharp
Domain
frontend, web-dev

Research direction

Read the linked issues #404, #421, #424 and #423, then inspect TaskDetailPage, the journal row in TodosSection, and TaskListRow to understand their shared changes. Start after the pipeline work listed in the issue; all four tasks need grooming, and #421 depends on a decision after #404. Done means each linked issue is closed or closed as not wanted with a one-line reason.

Written by the indexing model from the issue text.

Description

tech-debt

Groups the web-only usability issues around the task detail page and the Tasks page. They share files (TaskDetailPage, the journal row in TodosSection, TaskListRow), so they are built in one order and rebase onto each other once. None changes the API or the assistant.

Order

Do this group after the monorepo pipeline work (#397: #398, then #411, #399 and #400), so these issues are the first web features built with the merged pipeline. They are not blocked on GitHub: only the order says so.

  1. #404 — Open task details from journal rows and return to the same day (done, PR #462; #408 changes the same journal row and is tracked in #366)
  2. #421 — Click-through edit screen on the Tasks page instead of the inline editor above a long list (needs grooming; decide now that #404 is merged, since it replaces the inline editor with the detail page and shares its back-link rule)
  3. #424 — Change a task's journal day from the task details (needs grooming; the API already accepts journalDate on update, #352; check how it relates to the due date)
  4. #423 — Find a task by ID in every task search (needs grooming; independent, the smallest, can go any time in this group)

Why this order

  • #404, #421 and #424 all change the task detail page. #404 changes its back link, #421 makes editing a click-through to it, and #424 adds the day field to it. Built in this order, each rebases onto the last.
  • #423 edits the search boxes only, so it does not conflict with the others.

Notes

  • #404 moved here from #366 (an issue has one parent). Its link to #408 stays: both change the journal row in TodosSection.
  • #422 (planned subtasks hidden in get_journal) is not here: it is an assistant output change, tracked in #420.
  • All four need grooming first.

Done when

All four are closed or closed as not wanted, each with a one-line reason.

Dominant language
C#
Stars
1
Forks
0
Avg merge
2h 2m
Merged PRs (30d)
98

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from nevridge/TaskFlow

All issues in nevridge/TaskFlow

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.