Skip to content

[cueweb] Allocations link does not filter Monitor Hosts by allocation #2536

Description

@ramonfigueiredo

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:

  1. Go to CueCommander > Allocations.
  2. Click on any allocation name in the Name column.
  3. The Monitor Hosts page opens with the URL /hosts?allocation=<allocation name>.
  4. See that the allocation filter is not applied and the table lists hosts from every allocation.

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

Image Image

Version Number

Additional context

The query parameter names do not match on the two sides of the link:

  • cueweb/app/allocations/allocation-columns.tsx:52 builds the link as /hosts?allocation=`.
  • cueweb/app/hosts/page.tsx:124 seeds the allocation filter from a parameter named alloc (a comma separated list, parsed by parseSetParam).

Because allocation is 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 (the docs/_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 .md files:

Quick starts:

  • OpenCueWeb Quick Start: docs/_docs/quick-starts/quick-start-cueweb.md

Concepts:

  • OpenCueWeb and REST Gateway: docs/_docs/concepts/cueweb-rest-gateway.md

Getting started:

  • Deploying OpenCueWeb: docs/_docs/getting-started/deploying-cueweb.md

User guides:

  • OpenCueWeb User Guide: docs/_docs/user-guides/cueweb-user-guide.md

Other guides:

  • OpenCueWeb System: docs/_docs/other-guides/cueweb.md

Reference:

  • CueWeb Reference: docs/_docs/reference/cueweb.md

Tutorials:

  • OpenCueWeb Tutorial: docs/_docs/tutorials/cueweb-tutorial.md

Developer guide:

  • OpenCueWeb Development Guide: docs/_docs/developer-guide/cueweb-development.md

How 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) and docs/build.sh (local Ruby). From cd docs:

Option A: Docker (recommended, no Ruby needed)

cd docs
./docker-build.sh serve     # live-reload dev server at http://localhost:4000
./docker-build.sh build     # one-off build into docs/_site (this is your "test")
./docker-build.sh clean     # clean _site + docker artifacts
./docker-build.sh rebuild   # clean + build

(Equivalent via the Makefile: make serve, make build, make clean, make rebuild.)

Option B: Local Ruby (Ruby 3.0+ / Bundler)

cd docs
bundle install
./build.sh                              # test build: checks prereqs, runs jekyll build --verbose, checks image paths
bundle exec jekyll serve --livereload   # http://localhost:4000/

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).

Activity

  1. ramonfigueiredo commented on Sep 17, 2026

    @ramonfigueiredo
    CollaboratorAuthor

    CueWeb Documentation

    Quick starts

    Concepts

    Getting started

    User guides

    Other guides

    Reference

    Tutorials

    Developer guide

  2. ramonfigueiredo commented on Sep 17, 2026

    @ramonfigueiredo
    CollaboratorAuthor
    Image

    The 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:

    1. When opening a pull request, click the dropdown on the green “Create pull request” button and select “Create draft pull request”.
    2. Your PR will be clearly marked as Draft until you’re ready.
    3. 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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions