-
Notifications
You must be signed in to change notification settings - Fork 201
Add 'reason' field in the lock() step. #426
Copy link
Copy link
Open
Labels
Need testAutomated tests shall be extended.Automated tests shall be extended.extended propertiesIdeas about more aspects of the lockable resource instances than we had beforeIdeas about more aspects of the lockable resource instances than we had beforegood first issueGood for newcomersGood for newcomersnew parameters/featuresuiFeatures that may impact UI, pages made by the plugin or external UIs (BO, legacy, etc.)Features that may impact UI, pages made by the plugin or external UIs (BO, legacy, etc.)
Milestone
Description
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
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Need testAutomated tests shall be extended.Automated tests shall be extended.extended propertiesIdeas about more aspects of the lockable resource instances than we had beforeIdeas about more aspects of the lockable resource instances than we had beforegood first issueGood for newcomersGood for newcomersnew parameters/featuresuiFeatures that may impact UI, pages made by the plugin or external UIs (BO, legacy, etc.)Features that may impact UI, pages made by the plugin or external UIs (BO, legacy, etc.)
Type
Fields
Give feedbackNo fields configured for Enhancement.