This is an IBM Automation portal for Cloud Management and AIOps products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
I can create and update a release marker and it has a timestamp for start and last-updated. Is it possible to express a time range, to show up a long deployment?
At the moment, our pipelines create a release marker, after all pods in a rolling update were updated. (ArgoCD synced) If that release takes e.g. 5 min, I see lots of events while monitoring the deployment (scaling, traffic is reported with delay, and so on) and then the release marker is created.
I wish to be able to see a release timespan, so creating two release markers won't do it.
There already exists such a visualization but I cannot find an example right now. If there is a condition like a limit is reached, visualised by a chart, a red or purple bar below shows the time range, indicates that something happens in that time. That bar is as long as the time duration. Something like that would visualise the duration of a release and the user can map the events to the release which happens.
The Release-API would be like POSTing a new release marker, getting it's id in the response and after deployment is finished, I PUT an update with the end-timestamp.
Do not place IBM confidential, company confidential, or personal information into any field.