Problem
We have a requirement to populate List Box (dropdown) variable values dynamically before a release is created—i.e., the options must be resolved and shown to the user during the Create Release form stage.
Currently, List Box variables support only:

Fixed list, or
Value Provider, which can only pull from Applications / Environments defined within the Release tool itself.

This limitation doesn’t cover our use case, where the dropdown values need to come from external systems.
Use Case
We need the list values to be fetched and built dynamically by pulling and parsing data from third-party tools such as:

Jira
Confluence
GitLab
(e.g., projects, branches, tags, pages, tickets, component versions, etc.)

Ideally, this should be done via a custom script that runs at the Create Release Form stage, so end users can select from a dropdown of real-time, contextual data.
Proposed Enhancement
Add support for a new List variable source type, for example:

Script-based Value Provider (custom script / plugin / REST-backed provider)
Executed during Create Release form rendering / variable resolution
Returns a list of display values (and optionally IDs / key-value pairs)

Benefit
This would allow teams to build richer and more flexible release input forms, improving:

User experience (relevant dropdown options rather than manual text input)
Accuracy (selection from validated external data)
Efficiency (less manual validation and fewer errors)

by: YINFENG X. | 3 days ago | Templates & Releases