#242 No way to link to generic "current" blocker lists?
Closed: Invalid by kparal. Opened by ferdnyc.

This is somewhat related to #241, and solving that issue may make this one less urgent (or even unnecessary). But given the nature of the https://qa.fedoraproject.org/blockerbugs/ landing page, it may be more useful in documentation to link directly to the blocker listings.

But it doesn't appear that there's any way to link to "the current Beta blocker list" or "the current Final blocker list", in a generic fashion, since the release number is part of URLs like these:

  • https://qa.fedoraproject.org/blockerbugs/milestone/36/beta/buglist
  • https://qa.fedoraproject.org/blockerbugs/milestone/36/final/buglist

That makes those links unsuitable for documentation or other long-term sources. For those uses, ideally we'd be able to use links with implicit milestones, anything along the lines of:

  • https://qa.fedoraproject.org/blockerbugs/current/buglist
  • https://qa.fedoraproject.org/blockerbugs/current/beta/buglist
  • https://qa.fedoraproject.org/blockerbugs/milestone/current/beta/buglist

Metadata Update from @lbrabec:
- Issue assigned to lbrabec

We have that redirect available:
https://qa.fedoraproject.org/blockerbugs/current

Metadata Update from @kparal:
- Issue close_status updated to: Invalid
- Issue status updated to: Closed (was: Open)

@kparal

Indeed, I now see that I missed it way down at the bottom of blockerbugs/controllers/main.py. I'm tempted to reopen as "current-milestone redirect is undocumented", but I would've found it if I'd searched the source better so I'll let it go.

At least half of our documentation is obsolete, because we don't have any consumers, BlockerBugs App is a single-purpose project. So we only have some documentation for developers.

Instead of documentation, it would be better to have a button [Current blockers] on the landing page, which would fix two problems at once. I'll note that in #241.

This issue has been migrated to Fedora Forge:
https://forge.fedoraproject.org/quality/blockerbugs/issues/242

Please continue any further discussion there.

Log in to comment on this ticket.

Metadata