From 99d7fb7e3b340160cba1c8a5712f29983c6adcae Mon Sep 17 00:00:00 2001 From: Luis Toledo Date: Thu, 25 Jun 2026 15:08:58 -0400 Subject: [PATCH 1/2] RUN-4518: Document nodeFilter URL parameter for job linking Add nodeFilter to the supported query parameters in the "Linking to Jobs and providing option values" section. Includes the nodeFilterEditable requirement and a combined usage example. Co-Authored-By: Claude Sonnet 4.6 --- docs/manual/jobs/job-options.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/docs/manual/jobs/job-options.md b/docs/manual/jobs/job-options.md index 23cd50e44..ab099b76a 100644 --- a/docs/manual/jobs/job-options.md +++ b/docs/manual/jobs/job-options.md @@ -800,9 +800,10 @@ In this case, the option will be allowed to use a text field to set the value. You can create a URL to link to a specific Job, and pre-fill some of the option values by adding URL query parameters to the Job's URL. -Query Parameters format for options: +Supported query parameters: - `opt.NAME`: provide a value for an option named `NAME` +- `nodeFilter`: pre-populate the node filter field with the given filter expression. This parameter is only applied when the Job has **Node Filter** set to **Editable** (`nodeFilterEditable: true`); it is ignored otherwise. For example, if the URL for the Job is: @@ -816,4 +817,8 @@ The result would be: http://rundeck:4440/project/MyProject/job/show/ab698597-9753-4e98-bdab-90ebf395b0d0?opt.myopt1=some+value&opt.myotheropt=another+value +To also pre-populate the node filter, combine `nodeFilter` with option parameters: + + http://rundeck:4440/project/MyProject/job/show/ab698597-9753-4e98-bdab-90ebf395b0d0?opt.myopt1=some+value&nodeFilter=name%3A+web-server-01 + Note: be sure to properly escape the strings for option values, and if necessary for the option names as well. From 62fcedb0d31ae4149b57f1ce2cd16bd3b8e11ae3 Mon Sep 17 00:00:00 2001 From: Luis Toledo Date: Thu, 25 Jun 2026 15:34:33 -0400 Subject: [PATCH 2/2] RUN-4518: Expand URL encoding note to cover nodeFilter Per Copilot review: clarify that nodeFilter values also require URL encoding, with a concrete example of filter syntax characters. Co-Authored-By: Claude Sonnet 4.6 --- docs/manual/jobs/job-options.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/manual/jobs/job-options.md b/docs/manual/jobs/job-options.md index ab099b76a..3df587ed1 100644 --- a/docs/manual/jobs/job-options.md +++ b/docs/manual/jobs/job-options.md @@ -821,4 +821,4 @@ To also pre-populate the node filter, combine `nodeFilter` with option parameter http://rundeck:4440/project/MyProject/job/show/ab698597-9753-4e98-bdab-90ebf395b0d0?opt.myopt1=some+value&nodeFilter=name%3A+web-server-01 -Note: be sure to properly escape the strings for option values, and if necessary for the option names as well. +Note: be sure to properly URL-encode all parameter values. This applies to option values, option names, and `nodeFilter` expressions — filter syntax characters such as spaces and `:` must be encoded (e.g., `name: web-01` becomes `name%3A+web-01`).