This is an IBM Automation portal for Cloud Platform 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).
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:
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 updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
Hi Randy, I think the submitted idea was misunderstood. We are actually talking about the “Display name” and not the "Service name". I understand that the service name remains the same for both the new (v8.1.0.0) and older version (v7.3.1.1) of agents.
However, when I install a v8.1.0.0 agent in Windows, the display name is “DevOps Deploy Agent”. But when we upgrade a v7.3.1.1 agent to v8.1.0.0, it doesn’t change the display name to “DevOps Deploy Agent”.
This might lead to confusion because for new installed v8.1.0.0 agents, the display name is “DevOps Deploy Agent”, whereas for agents upgraded from the lower version (v7.3.1.1) to v8.1.0.0, the display name remains “IBM UCD Agent”.
We met with the development team and I wanted to provide some feedback. They told us it was a purposeful decision not to change the name of the Windows service on an upgrade. They said changing the service name could break the customers system. If you like, you can manually change the name of the service following the upgrade.
Thank you once more for opening this idea. We are creating a Jira discussion topic to review your request with our development team. Once completed, we will provide an update and we may have a question for you. The idea is now in the 'Under Review' state.
Thank you for submitting this Idea. Due to the holiday break that is beginning, we will review this as soon as possible. I will leave in the Submitted state for now, and at the right time, we will move to the Review state.