Skip to content

Add 'reason' field in the lock() step. #426

@mPokornyETM

Description

@mPokornyETM

What feature do you want to see added?

It will be very helpful, when we the lock() step allow to set the reason.
At the moment we can see that the resource is locked by some job. But when you have parallel stages it is hard to see which stage / node ... lock the resource.
In this case shall be this text shown in extra column in the table (or append to the STATE as well)
The text shall be pure String. No markUp or html format is necessary.

My first think was to use note as well, but this will leads to misunderstandings.

Upstream changes

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    Need testAutomated tests shall be extended.extended propertiesIdeas about more aspects of the lockable resource instances than we had beforegood first issueGood for newcomersnew parameters/featuresuiFeatures that may impact UI, pages made by the plugin or external UIs (BO, legacy, etc.)

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions