Package io.jenkins.plugins.batchcontrol.ui


package io.jenkins.plugins.batchcontrol.ui
  • Class
    Description
    Read-only display helpers for activation state (SPEC item 6a, D-46), shared by the job page, the computed-folder page and the activation screens.
    The refusal of a user-originated manual run of an approval-required job (SPEC item 6, e2e-03 DEF-02), thrown by the queue gate in place of a plain Failure.
    Reads the designated approver set from a submitted form (SPEC item 3, D-37).
    Computes the approver candidates shown in request forms: the global approver list intersected with the job-level restriction when one is configured (SPEC items 3 and 5).
    Minimal CSV emitter for the audit export endpoints (SPEC item 12).
    The plugin's only time-rendering vocabulary (U-07).
    D-66: request forms opened in core's dialog (data-type="dialog-opener" with data-dialog-url, the mechanism of core's "Create User" and build-parameters dialogs).
    One-line size summary of a stored unified diff, for the change-records screen (U-07).
    Parses and validates the history filter query parameters (SPEC item 12): from, to (ISO dates, inclusive), job (case-insensitive substring of the full name), user (exact id), result and status (enum-name tokens).
    The validated filter.
    The refusal of a submitted form, rendered on the form itself (SPEC section 6 usability line, e2e-03 DEF-09): the message sits next to the field it is about and what the user typed is kept.
    Links to the new grant request form on the Grants screen, prefilled for one item and one action (U-01 convention: new?scopeFullName=&actions=, D-66; D-71: a window names exactly one item, so there is no scope type).
    The refusal of a change that needs a permission window the user does not hold (SPEC item 8), for example the delete veto (e2e-03 DEF-26).
    What the strategy monitor says about an item in the "changed under a grant" state (D-58a/b): which permission window recorded the change, and after "Mark as reviewed" what still guards the item.
    The permission window that recorded a change to an item (or to a folder above it).
    What still guards an item after it was marked as reviewed.
    HTTP verb guard for the Batch Control URL spaces.
    D-71 (spec-review-S6 M-1): an item kind's icon as markup, for answers that are built in Java rather than in Jelly (the request form's item check, FormValidation.okWithMarkup).
    Paging arithmetic shared by every list screen (D-44).
    Resolves a record id that arrives as a URL segment (/batch-control/requests/<id>/ and the other detail URLs) or is about to become a link to one (S-39-01).
    Reads the values of a repeated form field (one value per entry, in submission order) from an application/x-www-form-urlencoded or a multipart/form-data body alike.
    D-58c: the runs of an item that were replayed under a permission window, for the two review surfaces (the batch-control-strategy monitor and the job's Batch Control page).
    One marked run: its id and its root-relative build URL, or null for plain text.
    D-38a: whether the requester of a run request (not the viewer) lacks Item/Build on the request's job, for the request detail page.
    D-60: carrying the values of a refused build submission into the job's Request Run form.
    D-38b: where BatchControl/Request is checked for a job-specific use (viewing, cancelling or re-designating a run or activation request, requesting an activation or hold): the request's item, so Request assigned on that job or a folder above it counts; Jenkins when the item no longer exists.
    Builds root-relative build URLs from stored identifiers, and small display helpers shared by the dashboard/incident/history views.
    D-75 (1), security-39 S-39-04 (SPEC item 8): the name a screen shows for the item of a grant request or permission window (tags/scopeItem.jelly).
    The permissions each Batch Control screen requires, in one place (SPEC item 2, hosting review).
    The tabs of the Batch Control page (hosting review 2026-10-02, PR6): one entry per section the current user may open, in a fixed order.
    One tab: a section of /batch-control/.
    Tells the saving user that the guard reverted the authorization part of their save (SPEC item 2, D-48, D-58a, D-58b): the item is guarded because a permission window covers it or it was changed under one and not yet reviewed, so a widening of its authorization is undone whoever saves it.
    Per-object visibility predicates for the request and grant screens (P-09, security review S-01).