When promotions take place and viewed, the configuration name appears in the promotion as shown below. Can there be another parameter called Label for example which would override this value and use it if defined. If left empty then default is configuration name.
Reason is if you create hierarchy like we have for example BETA/Promoted and PROD/Promoted as we have additional tasks under BETA and PROD, each of the promotion labels read Promtoed. We used to use the build name to include PROJECT_BETA_PROMOTED.001 and PROJECT_PROD_PROMOTED.002.
However now we are using version labels like 1.1 and so on and so it becomes hard to know where the promotions were done and also to read build pipelines.
The same label would prove to be really helpful for build pipelines arrangement and labelling as well. This could be a small enhancement request but from usage standpoint will be really awesome as it will truly allow QB to have a workflow with defined labels.
|
