This is an IBM Automation portal for Cloud Management, Technology Cost Management, Network Automation 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).
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.
As we currently don't see the wide benefit of having a free text-field just on the group details, without context where and how it could be used, we're not currently considering adding this to the roadmap.
This can be revised and revisited in the future.
Could you please give an example of what information you would currently store in a group description field?
Also, can you elaborate on where in the product or in which workflows you would need or use this additional information?
I assume new users are added through their SSO logins and our Group Mapping feature would automatically assign them to all the groups based on the rules defined and the users' attributes, so I'm just trying to understand what your current workflow is and where and how the description field would prove most useful.
If you are part of IBM:
You already have an older observability tool called IBM APM that has this capability. Perhaps you could connect with IBM APM and IBM Instana product personnel as to why they added it in APM, but never transferred similar capability in Instana.
If you aren't from IBM:
Allowing tool admins to add a description as part of a group is to better describe what the intentions of the group name is for. As a new user gets included, they will then get added to an appropriate group depending on the purpose of that group. And yes, because this capability doesn't exist today in Instana, it currently needs to be managed outside of the tool (AKA a workaround).
We'd love to better understand the problems to solve with this feature.
What kind of information would you want to save? In what context would you need access to this information, on which user flows?
Where do you use this in IBM APM today?
Is there any way you are managing such descriptions today for Instana? (ie postIT note, excel file, etc?)