Repository navigation
[cueweb] Allocations link does not filter Monitor Hosts by allocation #2536
Description
Activity
- addedbugSomething isn't workingSomething isn't working
on Sep 17, 2026 ramonfigueiredo commented
on Sep 17, 2026 CollaboratorAuthorMore actionsCueWeb Documentation
Quick starts
- REST Gateway Quick Start: https://docs.opencue.io/docs/quick-starts/quick-start-rest-gateway/
- OpenCueWeb Quick Start: https://docs.opencue.io/docs/quick-starts/quick-start-cueweb/
Concepts
- OpenCueWeb and REST Gateway: https://docs.opencue.io/docs/concepts/cueweb-rest-gateway/
Getting started
- Deploying OpenCue REST Gateway: https://docs.opencue.io/docs/getting-started/deploying-rest-gateway/
- Deploying OpenCueWeb: https://docs.opencue.io/docs/getting-started/deploying-cueweb
User guides
- OpenCue REST Gateway User Guide: https://docs.opencue.io/docs/user-guides/using-rest-api/
- OpenCueWeb User Guide: https://docs.opencue.io/docs/user-guides/cueweb-user-guide/
Other guides
- Production deployment/config of REST Gateway: https://docs.opencue.io/docs/other-guides/deploying-rest-gateway/
- OpenCueWeb System: https://docs.opencue.io/docs/other-guides/cueweb/
Reference
- OpenCue REST API Reference: https://docs.opencue.io/docs/reference/rest-api-reference/
- CueWeb Reference: https://docs.opencue.io/docs/reference/cueweb/
Tutorials
- REST API Tutorial: https://docs.opencue.io/docs/tutorials/rest-api-tutorial/
- OpenCueWeb Tutorial: https://docs.opencue.io/docs/tutorials/cueweb-tutorial/
Developer guide
- REST Gateway Development: https://docs.opencue.io/docs/developer-guide/rest-gateway-development/
- OpenCueWeb Development Guide: https://docs.opencue.io/docs/developer-guide/cueweb-development/
- OpenCueWeb README.md: https://github.com/AcademySoftwareFoundation/OpenCue/blob/master/cueweb/README.md
ramonfigueiredo commented
on Sep 17, 2026 CollaboratorAuthorMore actionsThe Academy Software Foundation (ASWF) Dev Days (https://www.aswf.io/dev-days/) is a fantastic way to contribute to the amazing and important #ASWF projects (https://www.aswf.io/projects/) that positively impact our industry. Whether you’re in #vfx, #animation, #softwareengineering, or #softwaredeveloper, this is a great opportunity to get involved.
📅 Dev Days: September 17th, 2026 (fully virtual, open worldwide)
For this event, we are highlighting OpenCue project - https://docs.opencue.io/, a production-proven render management system originally developed at Sony Pictures Imageworks and part of the ASWF. We’ve prepared easy issues and enhancements that are ideal for first-time contributors. These tasks are straightforward, designed to take less than a day to complete, and some can be finished in just a few hours. Everyone is invited to participate and contribute!
🔗 OpenCue codebase: https://github.com/AcademySoftwareFoundation/OpenCue
📘 OpenCue documentation: https://docs.opencue.io
📖 Developer guide: https://docs.opencue.io/docs/developer-guide/index/
🧪 Using the OpenCue Sandbox for Testing: https://docs.opencue.io/docs/developer-guide/sandbox-testing/
💬 OpenCue Slack channel: https://academysoftwarefdn.slack.com/archives/CMFPXV39Q
✅ Available tasks/issues and enhancements (good first issue + help wanted): https://github.com/AcademySoftwareFoundation/OpenCue/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22good%20first%20issue%22%20label%3A%22help%20wanted%22
✅ How to Contribute Effectively
- Focus on one issue at a time. Please don’t try to solve or implement all the main issues at once.
- When your work is complete, submit a full pull request (PR). We’ll review it as soon as possible.
- If your PR is not yet ready, submit it as a Draft Pull Request. Once you’re confident it’s ready, change the status to Open so maintainers know it can be reviewed.
How to create a Draft PR on GitHub:
- When opening a pull request, click the dropdown on the green “Create pull request” button and select “Create draft pull request”.
- Your PR will be clearly marked as Draft until you’re ready.
- When it’s ready for review, click “Ready for review” at the top of the PR page - this changes the status to Open.
Thank you for your contribution!
Before we can move forward with the code review, please sign the CLA Authorization - EasyCLA➡️ You only need to sign the CLA once, when you are submitting your first full request to the OpenCue project. After that, you’re all set for future contributions.
Everyone’s collaboration is very much appreciated. Thank you for helping grow OpenCue and for contributing to the software our industry relies on!
Describe the bug
On the Allocations page each allocation name is a link to the Monitor Hosts page, but the destination page loads every host in the cue instead of only the hosts that belong to the allocation that was clicked.
To Reproduce
Steps to reproduce the behavior:
/hosts?allocation=<allocation name>.Expected behavior
Following the link opens Monitor Hosts pre filtered to the allocation that was clicked, so the user immediately sees exactly which hosts are in that allocation. The active filter should be visible in the Monitor Hosts filter controls so the user can clear or widen it.
Screenshots
Version Number
Additional context
The query parameter names do not match on the two sides of the link:
cueweb/app/allocations/allocation-columns.tsx:52builds the link as /hosts?allocation=`.cueweb/app/hosts/page.tsx:124seeds the allocation filter from a parameter namedalloc(a comma separated list, parsed byparseSetParam).Because
allocationis never read, the filter starts empty and the table renders unfiltered. The fix is to emit?alloc=<name>from the Allocations link, or to accept both parameter names on the Monitor Hosts page. A source comment next to the link notes that the hosts side filter was deferred, so this looks like an unfinished hand off rather than a regression.Documentation to update
Please update the affected OpenCue/CueWeb docs and refresh their screenshots to match the new interface.
Screenshots live in
docs/assets/images/cueweb/and are referenced from the docs as/assets/images/cueweb/<name>.png(thedocs/_site/...copies are generated Jekyll output, do not edit those). Follow the existing naming (cueweb_<area>_<description>.png) and add a matching dark-mode variant (..._dark.png) where the page shows one. Replace the relevant existing images, and add new ones for new screens, so the published pages match the shipped UI.Not every page applies to every issue; update the ones the change affects.
The published pages and their source
.mdfiles:Quick starts:
docs/_docs/quick-starts/quick-start-cueweb.mdConcepts:
docs/_docs/concepts/cueweb-rest-gateway.mdGetting started:
docs/_docs/getting-started/deploying-cueweb.mdUser guides:
docs/_docs/user-guides/cueweb-user-guide.mdOther guides:
docs/_docs/other-guides/cueweb.mdReference:
docs/_docs/reference/cueweb.mdTutorials:
docs/_docs/tutorials/cueweb-tutorial.mdDeveloper guide:
docs/_docs/developer-guide/cueweb-development.mdHow to test the documentation locally?
The OpenCue documentation is a Jekyll site in docs/, and there are two build scripts:
docs/docker-build.sh(recommended) anddocs/build.sh(local Ruby). From cd docs:Option A: Docker (recommended, no Ruby needed)
(Equivalent via the Makefile: make serve, make build, make clean, make rebuild.)
Option B: Local Ruby (Ruby 3.0+ / Bundler)
Screenshots you drop into docs/assets/images/cueweb/ and reference as /assets/images/cueweb/.png will appear on live reload. Please don't touch docs/_site/ (it's generated output).