Our pipelines sometimes fail for expected reasons, but which are only obvious to DevOps people (like publish failure because of artifact version conflict which manifests itself with an apparently unrelated error).
Is there a way to set a user-friendly status message in the pipeline details page, like what happens when a step runs out of memory? This would avoid developers having to reach out to IT to interpret the failure from thousands of log lines every time even if we try to catch the error and output something less cryptic.