It seems impossible to create milestones in the admin interface right now (in whatever's deployed to production). When you try to create a milestone, the form you're shown has no "release" field, as it used to. If you ignore that and try to create the milestone, you get an error "Failed to create model. 'MilestoneForm' object has no attribute 'release'".
We need this fixed before F39 Final is done or else we won't be able to track F40 blockers.
I do wonder if a7310ec is the culprit here - I think the change:
- release_id = db.Column(db.Integer, db.ForeignKey('release.id')) + release_id: db.Mapped[Optional[int]] = db.mapped_column(db.ForeignKey('release.id'))
i.e. making the "release_id" option for the Milestone class might be the issue? @kparal
Ugh, thanks for a report, I'll look at it.
or else we won't be able to track F40 blockers
We should still be able to create milestones using a command line on the server. If you wish, we can do it right away.
Issue tagged with: next
@adamwill I've added F40 FE/Blocker to the prod deployment, will leave this ticket open as the underlying issue isn't fixed yet.
Metadata Update from @kparal: - Issue untagged with: next - Issue priority set to: High (was: Critical)
Ping? We kinda need to add the F41 trackers, I can't because of this.
@frantisekz Can you please add F41 milestones using the cmdline?
Yeah, I can (and will) add it via the cmdline in a bit, but let this be a reminder of this though 😁
Also, it's possible this entire process to be handled automatically, as we do so in oraculum: https://pagure.io/fedora-qa/oraculum/blob/master/f/oraculum/utils/bugzilla.py#_29-72
Added, should appear in the next sync window. Assigning to @kparal now for a proper fix, if you no longer want to work on this, feel free to remove the assignment.
Metadata Update from @frantisekz: - Issue assigned to kparal
Metadata Update from @kparal: - Assignee reset - Custom field story_points adjusted to 3
This issue has been migrated to Fedora Forge: https://forge.fedoraproject.org/quality/blockerbugs/issues/279
Please continue any further discussion there.
Log in to comment on this ticket.