forge/forge
9
0
Fork 1
Code Issues 58 Pull requests Projects 3 Wiki Activity Actions

Pagure migration incorrectly sets due dates for milestones #281

New issue
Closed
opened 2025-11-14 14:14:06 +00:00 by kparal · 13 comments
kparal commented 2025-11-14 14:14:06 +00:00
Copy link

All milestones for a project that I migrated from Pagure (source, target) have the Due date set for all milestones at 01/01/0001 (I see this when editing the milestone; in the regular view, I just see a dash, probably meaning "incorrect date").

There seems to be some problem when migrating the dates.

All milestones for a project that I migrated from Pagure ([source](https://pagure.io/fedora-qa/roadmap?status=all), [target](https://forge.stg.fedoraproject.org/quality/tickets/milestones?state=open&q=&sort=closestduedate)) have the _Due date_ set for all milestones at `01/01/0001` (I see this when editing the milestone; in the regular view, I just see a dash, probably meaning "incorrect date"). There seems to be some problem when migrating the dates.
ryanlerch added this to the Backlog project 2025-11-17 10:20:22 +00:00
ryanlerch modified the project from Backlog to Sprint 12 2025-11-18 01:51:20 +00:00
t0xic0der commented 2025-11-19 08:34:46 +00:00
Member
Copy link

Associated PR. https://codeberg.org/fedora/forgejo/pulls/80

Associated PR. https://codeberg.org/fedora/forgejo/pulls/80
t0xic0der commented 2025-11-19 08:38:59 +00:00
Member
Copy link

Here's how the change works.

At source

image

At destination

image

image

Here's how the change works. At source ![image](/attachments/c51b1b12-fa76-4dfe-a392-d1553a73ece8) At destination ![image](/attachments/8f0b7480-7353-4431-b55f-a9f24d950d50) ![image](/attachments/90b97c6e-cd61-4898-b44b-793db2b2bf71)
image.png
74 KiB
image.png
73 KiB
image.png
70 KiB
kparal commented 2025-11-19 13:32:49 +00:00
Author
Copy link

Huh, I had no idea that Pagure milestones can be configured with unix timestamps 🙂 Will it work for YYYY-MM-DD (as we use it) as well?

Huh, I had no idea that Pagure milestones can be configured with unix timestamps 🙂 Will it work for YYYY-MM-DD (as we use it) as well?
t0xic0der commented 2025-11-20 06:32:22 +00:00
Member
Copy link

I am uncertain as to which is the default. Pagure just had a textbox. I can make it work with YYYY-MM-DD as well but I need more info on this as there might be other formats used by others too. @ryanlerch, have you got ideas?

I am uncertain as to which is the default. Pagure just had a textbox. I can make it work with `YYYY-MM-DD` as well but I need more info on this as there might be other formats used by others too. @ryanlerch, have you got ideas?
t0xic0der commented 2025-11-20 06:36:35 +00:00
Member
Copy link

Associated PR. https://codeberg.org/forgejo/forgejo/pulls/10169

Associated PR. https://codeberg.org/forgejo/forgejo/pulls/10169
kparal commented 2025-11-28 13:20:01 +00:00
Author
Copy link

If the fields in Pagure milestones are just a text box, it's very unlikely that anyone would use unix timestamps, because that would be unreadable for humans. So if anything, I'd love to see at least the most common YYYY-MM-DD to be implemented, thanks a lot.

If the fields in Pagure milestones are just a text box, it's very unlikely that anyone would use unix timestamps, because that would be unreadable for humans. So if anything, I'd love to see at least the most common `YYYY-MM-DD` to be implemented, thanks a lot.
t0xic0der commented 2025-12-01 11:46:07 +00:00
Member
Copy link

I would additionally add support for YYYY-MM-DD but restrict the scope of the ticket there only as the milestone dates on Pagure are not semantic in nature. Thanks!

I would additionally add support for `YYYY-MM-DD` but restrict the scope of the ticket there only as the milestone dates on Pagure are not semantic in nature. Thanks!
kparal commented 2025-12-01 13:50:29 +00:00
Author
Copy link

Sorry, I don't understand. Is YYYY-MM-DD implemented now? I'm waiting for this before we migrate our main QA tickets repo, because I don't want to fix all the milestones by hand.

Sorry, I don't understand. Is `YYYY-MM-DD` implemented now? I'm waiting for this before we migrate our main QA tickets repo, because I don't want to fix all the milestones by hand.
kparal commented 2025-12-10 09:07:04 +00:00
Author
Copy link

@t0xic0der Now that #306 is closed, I tested it on forge.stg and it still doesn't work. Should this be already deployed? If not, please tell me when, so that I can test it. Thanks.

@t0xic0der Now that #306 is closed, I tested it on forge.stg and it still doesn't work. Should this be already deployed? If not, please tell me when, so that I can test it. Thanks.
kparal commented 2026-01-08 09:33:14 +00:00
Author
Copy link

This is still not working with https://pagure.io/fedora-qa , reopening. @t0xic0der Can you please look into this?

This is still not working with https://pagure.io/fedora-qa , reopening. @t0xic0der Can you please look into this?
kparal reopened this issue 2026-01-08 09:33:15 +00:00
t0xic0der commented 2026-01-12 11:04:27 +00:00
Member
Copy link

@kparal, this change is expected to be shipped with Forgejo v14.0.0 release as mentioned in this milestone associated with the pull request that I have sent upstream. We have Forgejo v13.0.3-10 deployed at the time of writing this issue comment. Could you please wait until the changes roll in this deployment before you attempt migrating again? Alternatively, you could consider reaching out to the upstream to see if they can ship this change at the earliest possible. Thanks!

@kparal, this change is expected to be shipped with Forgejo v14.0.0 release as mentioned in this milestone associated with the [pull request](https://codeberg.org/forgejo/forgejo/pulls/10299#issuecomment-9138804) that I have sent upstream. We have [Forgejo v13.0.3-10](https://codeberg.org/forgejo/forgejo/src/branch/forgejo/release-notes-published/13.0.3.md) deployed at the time of writing this issue comment. Could you please wait until the changes roll in this deployment before you attempt migrating again? Alternatively, you could consider reaching out to the upstream to see if they can ship this change at the earliest possible. Thanks!
t0xic0der commented 2026-01-12 11:07:50 +00:00
Member
Copy link

@kparal, I am opening another issue ticket that specifically tracks the deployment of this change. Rest assured, we will ensure that this change gets to us - either as soon as possible or whenever it is slated. Thanks!

@kparal, I am opening another issue ticket that specifically tracks the deployment of this change. Rest assured, we will ensure that this change gets to us - either as soon as possible or whenever it is slated. Thanks!
kparal commented 2026-01-13 11:23:36 +00:00
Author
Copy link

@t0xic0der wrote in #281 (comment):

this change is expected to be shipped with Forgejo v14.0.0 release

Thanks for checking. Forgejo 14 milestone is currently marked for Jan 15th. We'll wait.

@t0xic0der wrote in https://forge.fedoraproject.org/forge/forge/issues/281#issuecomment-260871: > this change is expected to be shipped with Forgejo v14.0.0 release Thanks for checking. [Forgejo 14 milestone](https://codeberg.org/forgejo/forgejo/milestone/27583) is currently marked for Jan 15th. We'll wait.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
test
docs
No results found.
Labels
Clear labels   
Backlog Status
Needs Review
Work items that have been created or updated but need review, refinement, or approval before they can be considered ready for sprint planning.

  
Backlog Status
Ready
Work items that have been reviewed, refined, and are ready to be committed to a sprint. These items have clear requirements and could be worked on immediately when capacity is available.

  
Chore

Tasks that are necessary but don't directly deliver new value to the end-user. These are internal tasks like updating a library, managing user accounts, or setting up a new service.

  
points
01
A task that is simple, small, and has very little uncertainty. It should be easy enough for any team member to pick up and complete quickly, without a lot of discussion or research.

  
points
02
This is a task that is slightly more complex or larger than a "1." It might involve two or three simple steps, but the outcome is still very clear and there's little uncertainty.

  
points
03
medium-sized task with some noticeable complexity. It might require a bit more thought or collaboration. The steps are well-defined, but it's not a trivial change.

  
points
05
a significant piece of work. It has more complexity and a higher degree of uncertainty than smaller tasks. It might require some research, a design discussion, or collaboration across multiple teams.

  
points
08
complex task with a lot of uncertainty. It's often the largest size that a team will consider for a single sprint. It likely requires a detailed breakdown and multiple team members to complete.

  
points
13
Any task that feels like it's a "13" or more is considered an Epic. These are too large and uncertain to be worked on in a single sprint.

  
Priority
High
This is for work that is critical and needs to be addressed in the next sprint. It's often for urgent bugs, important features, or a major piece of technical debt that is blocking other work.

  
Priority
Low
This is for work that is good to do but not urgent. It's a candidate for being worked on when there's extra time or when it rises in importance. It can stay in the backlog for a longer period.

  
Priority
Medium
This is for important work that should be done soon, but isn't as urgent as a high-priority item. It will likely be considered for the next 1-2 sprints.

  
Sprint Status
Blocked
Indicates the work cannot proceed. There is a dependency or an issue that is preventing the team from completing the task. This is a flag for the Scrum Master to help unblock the team.

  
Sprint Status
Done
Work items that have been completed, reviewed, and integrated. No further work is needed within the current sprint.

  
Sprint Status
In Progress
This label is for work that a developer is actively working on. This is usually what you'll see on the "In Progress" column of your project board.

  
Sprint Status
Review
This indicates that the work is complete, but it is now in a review state. This could mean a peer code review, a QA check, or a review by the Product Owner.

  
Sprint Status
To Do
Work items that are committed to the sprint but haven't been started yet. These items are ready to be picked up by team members.

  
Technical Debt

work that improves the codebase without adding new features. It's work that pays down the "debt" you've accumulated, such as refactoring a messy piece of code, improving test coverage.

  
Work Item
Bug
Issues where the system is not working as intended or designed. Bugs represent deviations from expected behavior.

  
Work Item
Epic

  
Work Item
Spike

  
Work Item
Task

  
Work Item
User Story

  
Backlog Status
Needs Review
Work items that have been created or updated but need review, refinement, or approval before they can be considered ready for sprint planning.

  
Backlog Status
Ready
Work items that have been reviewed, refined, and are ready to be committed to a sprint. These items have clear requirements and can be worked on immediately when capacity is available.

  
chore

Work that needs to be done but doesn't add new functionality or fix bugs. Maintenance tasks that keep the system running smoothly and the codebase clean.

  
documentation

Work focused on creating, updating, or improving documentation for users, developers, or system administrators.

  
points
01
A task that is simple, small, and has very little uncertainty. It should be easy enough for any team member to pick up and complete quickly, without a lot of discussion or research.

  
points
02
This is a task that is slightly more complex or larger than a "1." It might involve two or three simple steps, but the outcome is still very clear and there's little uncertainty.

  
points
03
Medium-sized task with some noticeable complexity. It might require a bit more thought or collaboration. The steps are well-defined, but it's not a trivial change.

  
points
05
A significant piece of work. It has more complexity and a higher degree of uncertainty than smaller tasks. It might require some research, a design discussion, or collaboration across multiple teams.

  
points
08
Complex task with a lot of uncertainty. It's often the largest size that a team will consider for a single sprint. It likely requires a detailed breakdown and multiple team members to complete.

  
points
13
Any task that feels like it's a "13" or more is considered an Epic. These are too large and uncertain to be worked on in a single sprint and should be broken down.

  
Priority
High
This is for work that is critical and needs to be addressed in the next sprint. It's often for urgent bugs, important features, or a major piece of technical debt that is blocking other work.

  
Priority
Low
This is for work that is good to do but not urgent. It's a candidate for being worked on when there's extra time or when it rises in importance. It can stay in the backlog for a longer period.

  
Priority
Medium
This is for important work that should be done soon, but isn't as urgent as a high-priority item. It will likely be considered for the next 1-2 sprints.

  
Sprint Status
Blocked
Work items that cannot progress due to external dependencies, blockers, or issues that need resolution.

  
Sprint Status
Done
Work items that have been completed, reviewed, and integrated. No further work is needed within the current sprint.

  
Sprint Status
In Progress
Work items currently being worked on by a team member. Active development, research, or implementation is happening.

  
Sprint Status
Review
Work items that are complete but need review, testing, or approval before being marked as done.

  
Sprint Status
To Do
Work items that are committed to the sprint but haven't been started yet. These items are ready to be picked up by team members.

  
Technical Debt

Work that addresses shortcuts, workarounds, or suboptimal implementations that were done previously to meet deadlines. These items improve code quality, maintainability, or performance without adding new features.

  
Work Item
Bug
Issues where the system is not working as intended or designed. Bugs represent deviations from expected behavior.

  
Work Item
Epic
Large initiatives that are broken down into multiple smaller work items (user stories, tasks, bugs). Epics represent significant features or projects that span multiple sprints.

  
Work Item
Spike
Time-boxed research, investigation, or proof-of-concept work to reduce uncertainty or explore solutions. Spikes help inform future development decisions.

  
Work Item
Task
Used to break down larger user stories into smaller, manageable implementation pieces. They focus on the specific technical steps needed to deliver the user story's value.

  
Work Item
User Story
User-facing features or functionality that can be framed from a user perspective, describing what someone wants to accomplish and why.

No labels
Backlog Status
Needs Review
Backlog Status
Ready
Chore
points
01
points
02
points
03
points
05
points
08
points
13
Priority
High
Priority
Low
Priority
Medium
Sprint Status
Blocked
Sprint Status
Done
Sprint Status
In Progress
Sprint Status
Review
Sprint Status
To Do
Technical Debt
Work Item
Bug
Work Item
Epic
Work Item
Spike
Work Item
Task
Work Item
User Story
Backlog Status
Needs Review
Backlog Status
Ready
chore
documentation
points
01
points
02
points
03
points
05
points
08
points
13
Priority
High
Priority
Low
Priority
Medium
Sprint Status
Blocked
Sprint Status
Done
Sprint Status
In Progress
Sprint Status
Review
Sprint Status
To Do
Technical Debt
Work Item
Bug
Work Item
Epic
Work Item
Spike
Work Item
Task
Work Item
User Story
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Sprint 10 Archive
Assignees
Clear assignees
No assignees
t0xic0der
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.

Blocks
#306 Extend support for YYYY-MM-DD format for Pagure milestones and document manual testing for the same
forge/forge
#336 Verify if the milestone dates are set correctly in the production deployment of Fedora Forge
forge/forge
Reference
forge/forge#281
No description provided.