Add devlog timeline of related posts to project page #135

New Issue
Closed
opened 2026-07-25 09:09:38 +02:00 by retoor · 17 comments
retoor commented 2026-07-25 09:09:38 +02:00
Owner
Copy Link

Summary

Project page lacks a timeline of all posts related to the project. Add a "Devlog" tab that lists posts in reverse chronological order.

Steps to Reproduce

Not provided.

Expected Behaviour

When viewing a project page, there is a "Devlog" or "Posts" section that displays all posts tagged/attached to that project in reverse chronological order. When creating a post, users can link it to a project (similar to existing project_uid field). Visitors can see the full project history (initial announcement, updates, release notes, etc.).

Actual Behaviour

Currently, posts can be attached to a project during creation, but the project page does not display these posts. Users must manually search for posts related to the project.

Environment

Not provided.

Reported by blindxfish via DevPlace.

## Summary Project page lacks a timeline of all posts related to the project. Add a "Devlog" tab that lists posts in reverse chronological order. ## Steps to Reproduce Not provided. ## Expected Behaviour When viewing a project page, there is a "Devlog" or "Posts" section that displays all posts tagged/attached to that project in reverse chronological order. When creating a post, users can link it to a project (similar to existing project_uid field). Visitors can see the full project history (initial announcement, updates, release notes, etc.). ## Actual Behaviour Currently, posts can be attached to a project during creation, but the project page does not display these posts. Users must manually search for posts related to the project. ## Environment Not provided. --- *Reported by **blindxfish** via DevPlace.*
plan-ticket-135.md
4.0 KiB
typosaurus commented 2026-07-25 09:11:36 +02:00
Collaborator
Copy Link

I am picking this ticket up now.

First I will bring up an isolated workspace with a fresh checkout and investigate whether the ticket matches the current state of the code before planning any change. I will announce every step here before I take it.

I am picking this ticket up now. First I will bring up an isolated workspace with a fresh checkout and investigate whether the ticket matches the current state of the code before planning any change. I will announce every step here before I take it.
typosaurus commented 2026-07-25 09:12:41 +02:00
Collaborator
Copy Link

Starting research round 1 of at most 5.

I am now reading the relevant source, tests, and prior work in the live checkout to verify the ticket and gather the context needed for a concrete plan. This can take a while; I will post periodic progress updates until it completes.

Starting research round 1 of at most 5. I am now reading the relevant source, tests, and prior work in the live checkout to verify the ticket and gather the context needed for a concrete plan. This can take a while; I will post periodic progress updates until it completes.
typosaurus commented 2026-07-25 09:16:58 +02:00
Collaborator
Copy Link

Investigated the ticket against the current source and tests. The research confirms that posts can be linked to projects via project_uid, but the project detail page lacks any listing of those posts. No schema field, query, template, or CSS exists to support a timeline. The reporter’s scope matches this gap, and no clarifications are needed.

Decision is to proceed. The next step is drafting a concrete implementation plan covering schema extension, query logic, template changes, and styling.

Investigated the ticket against the current source and tests. The research confirms that posts can be linked to projects via `project_uid`, but the project detail page lacks any listing of those posts. No schema field, query, template, or CSS exists to support a timeline. The reporter’s scope matches this gap, and no clarifications are needed. Decision is to proceed. The next step is drafting a concrete implementation plan covering schema extension, query logic, template changes, and styling.
typosaurus commented 2026-07-25 09:17:06 +02:00
Collaborator
Copy Link

I am drafting the implementation plan now.

The research confirmed the ticket; I am turning the findings into a concrete, verifiable plan.

I am drafting the implementation plan now. The research confirmed the ticket; I am turning the findings into a concrete, verifiable plan.
typosaurus commented 2026-07-25 09:17:32 +02:00
Collaborator
Copy Link

Drafted an implementation plan from the investigation findings. The plan covers schema indexing, schema updates, router logic, template changes, CSS styling, and a new test to add a Devlog tab showing related posts on the project page. This resolves the requirement to display a timeline of posts attached to a project.

Handing the plan to the execution agent for implementation.

Drafted an implementation plan from the investigation findings. The plan covers schema indexing, schema updates, router logic, template changes, CSS styling, and a new test to add a Devlog tab showing related posts on the project page. This resolves the requirement to display a timeline of posts attached to a project. Handing the plan to the execution agent for implementation.
typosaurus commented 2026-07-25 09:17:32 +02:00
Collaborator
Copy Link

The full, verbatim implementation plan is attached: plan-ticket-135.md

The full, verbatim implementation plan is attached: [plan-ticket-135.md](https://retoor.molodetz.nl/attachments/807c9601-798d-4213-b095-68a0bb6014a7)
typosaurus commented 2026-07-25 09:17:37 +02:00
Collaborator
Copy Link

Starting implementation attempt 1 of at most 5.

I am executing the plan inside this ticket's isolated workspace. This can take a while; I will post periodic progress updates until it completes.

Starting implementation attempt 1 of at most 5. I am executing the plan inside this ticket's isolated workspace. This can take a while; I will post periodic progress updates until it completes.
typosaurus commented 2026-07-25 09:23:47 +02:00
Collaborator
Copy Link

Implementation attempt 1 finished; I am verifying it now.

Running the project's own build, test, and lint commands against the change.

Implementation attempt 1 finished; I am verifying it now. Running the project's own build, test, and lint commands against the change.
typosaurus commented 2026-07-25 09:23:50 +02:00
Collaborator
Copy Link

The change was implemented on the first attempt, and all configured project checks — build, test, and lint commands — completed successfully.

The next step is to commit the changes, push the branch, and open a pull request for review.

The change was implemented on the first attempt, and all configured project checks — build, test, and lint commands — completed successfully. The next step is to commit the changes, push the branch, and open a pull request for review.
typosaurus commented 2026-07-25 09:23:51 +02:00
Collaborator
Copy Link

I am delivering the change now.

Committing the verified change, pushing branch typosaurus/ticket-135, and opening a pull request.

I am delivering the change now. Committing the verified change, pushing branch `typosaurus/ticket-135`, and opening a pull request.
typosaurus commented 2026-07-25 09:23:58 +02:00
Collaborator
Copy Link

The change has been committed, the branch typosaurus/ticket-135 pushed, and a pull request opened at #136.

The implementation passed the project's own checks, so the work is ready for review.

Next steps are to monitor the pull request for review, merge, or any additional feedback.

The change has been committed, the branch `typosaurus/ticket-135` pushed, and a pull request opened at https://retoor.molodetz.nl/retoor/devplacepy/pulls/136. The implementation passed the project's own checks, so the work is ready for review. Next steps are to monitor the pull request for review, merge, or any additional feedback.
typosaurus self-assigned this 2026-07-26 22:07:03 +02:00
typosaurus commented 2026-07-26 22:08:21 +02:00
Collaborator
Copy Link

YELENA · project-manager — 2026-07-26T20:08:20.248374+00:00

Ticket claimed by team Dev Team ONE ELITE.
Branch: typosaurus/135-add-devlog-timeline-of-related-posts-to-project-page
Agents assigned: @yelena, @katya, @mila, @vera, @nadia, @sveta, @tanya, @zoya, @irina, @oksana, @larisa
Next: Decompose the ticket into an executable tree.

<!-- typosaurus:claim run=45c0aee6df2649ffaa248729bdfd5841 id=47965b93446e team=e128e22619ab46999074678e27b7e0f7 --> **YELENA · project-manager** — 2026-07-26T20:08:20.248374+00:00 Ticket claimed by team Dev Team ONE ELITE. Branch: typosaurus/135-add-devlog-timeline-of-related-posts-to-project-page Agents assigned: @yelena, @katya, @mila, @vera, @nadia, @sveta, @tanya, @zoya, @irina, @oksana, @larisa Next: Decompose the ticket into an executable tree.
typosaurus commented 2026-07-26 22:14:07 +02:00
Collaborator
Copy Link

YELENA · project-manager — 2026-07-26T22:03:38.939215+00:00

Progress

State: running
Completed: 7/7 nodes
Current: none — none
Cost: 0.1191 USD · Elapsed: 1h 55m

Completed

  • Add devlog timeline of related posts to project page — done
  • Investigate existing patterns for devlog — done
  • Add database index and devlog query helper — done
  • Add devlog route logic and schema update — done
  • Add devlog section to project detail template — done
  • Write tests for devlog timeline — done
  • Review implementation against acceptance criteria — done

Open

  • none
<!-- typosaurus:progress run=45c0aee6df2649ffaa248729bdfd5841 id=82a9479e65bf team=e128e22619ab46999074678e27b7e0f7 --> **YELENA · project-manager** — 2026-07-26T22:03:38.939215+00:00 ## Progress State: running Completed: 7/7 nodes Current: none — none Cost: 0.1191 USD · Elapsed: 1h 55m ### Completed - Add devlog timeline of related posts to project page — done - Investigate existing patterns for devlog — done - Add database index and devlog query helper — done - Add devlog route logic and schema update — done - Add devlog section to project detail template — done - Write tests for devlog timeline — done - Review implementation against acceptance criteria — done ### Open - none
typosaurus commented 2026-07-27 00:04:01 +02:00
Collaborator
Copy Link

YELENA · project-manager — 2026-07-26T22:04:01.444191+00:00

Result

Run completed for ticket #135.

Delivered:

  • The ticket objective is satisfied: Add devlog timeline of related posts to project page — met (see commits)

Not delivered:

  • none

Verification: make test — see nodes
Commits: 4 · Cost: 0.1040 USD · Duration: 1h 55m
Pull request: #141

<!-- typosaurus:summary run=45c0aee6df2649ffaa248729bdfd5841 id=f8b9df7c183e team=e128e22619ab46999074678e27b7e0f7 --> **YELENA · project-manager** — 2026-07-26T22:04:01.444191+00:00 ## Result Run completed for ticket #135. Delivered: - The ticket objective is satisfied: Add devlog timeline of related posts to project page — met (see commits) Not delivered: - none Verification: make test — see nodes Commits: 4 · Cost: 0.1040 USD · Duration: 1h 55m Pull request: https://retoor.molodetz.nl/retoor/devplacepy/pulls/141
typosaurus commented 2026-07-27 00:04:10 +02:00
Collaborator
Copy Link

YELENA · project-manager — 2026-07-26T22:04:10.559629+00:00

Result

Run completed for ticket #135.

Delivered:

  • The ticket objective is satisfied: Add devlog timeline of related posts to project page — met (see commits)

Not delivered:

  • none

Verification: make test — see nodes
Commits: 4 · Cost: 0.1040 USD · Duration: 1h 55m
Pull request: #141

<!-- typosaurus:summary run=45c0aee6df2649ffaa248729bdfd5841 id=97fd14fa78a1 team=e128e22619ab46999074678e27b7e0f7 --> **YELENA · project-manager** — 2026-07-26T22:04:10.559629+00:00 ## Result Run completed for ticket #135. Delivered: - The ticket objective is satisfied: Add devlog timeline of related posts to project page — met (see commits) Not delivered: - none Verification: make test — see nodes Commits: 4 · Cost: 0.1040 USD · Duration: 1h 55m Pull request: https://retoor.molodetz.nl/retoor/devplacepy/pulls/141
typosaurus commented 2026-07-27 00:53:05 +02:00
Collaborator
Copy Link

The ticket has been closed and work has been stopped. No further action is planned at this time.

The ticket has been closed and work has been stopped. No further action is planned at this time.
typosaurus commented 2026-07-27 00:53:05 +02:00
Collaborator
Copy Link

This ticket has reached its outcome. The ticket is closed and the workspace is no longer needed.

Would you like me to clean up the branch and workspace for this ticket? Reply with /typosaurus cancel-and-cleanup to confirm, or leave it as is.

This ticket has reached its outcome. The ticket is closed and the workspace is no longer needed. Would you like me to clean up the branch and workspace for this ticket? Reply with `/typosaurus cancel-and-cleanup` to confirm, or leave it as is.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
typosaurus
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: retoor/devplacepy#135
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?