Add the capability to add multiple Group segments in a plug-in

[jelaplan]

Goal: Add the capability to add multiple Group segments in a plug-in. When teams build plug-ins, the plug-in name ends up as the group name (for example, zowe cics). We have referred to this as the lost-group problem. This means that your plugin can't have separate groups to divide content - groups are essentially categories of commands. A workaround that has been used is to append a group name to the action name (for example, category-action, jobs-list, or files-list). This may or may not be desirable but has draw backs in terms of unwieldy and abstract names. To escape the lost-group problem and avoid actions with compound names, teams can create separate plug-ins.

See the Command Format Standards

Overarching problem: Improving the Findability and Discoverability of Capabilities and Functionality. We hear customers explain that they can't find what they are looking for. Also they don't understand the capabilities of the CLI so we need better ways to reveal that information.

Some details:

• This would allow us to elegantly combine the two extended plugins.
• This would give plug-in developers a powerful capability when creating plugins.
• We see teams like the IBM CICS team creating a second CICS plugin and I wonder if we had this multi-group capability, it be more palatable to extend the existing plugin with a second group.

[Joe-Winchester]

+1 for this issue. I have quite a few teams asking why core Zowe should be special zowe files, zowe jobs, ... but that extensions are limited to just one group for their plugin.

[github-actions[bot]]

Thank you for raising this issue. The community has 90 days to upvote 👍 the issue. If it receives 5 upvotes, we will move it to our backlog. If not, we will close it.

[github-actions[bot]]

Thank you for raising this enhancement request. The community has 90 days to vote on it. If the enhancement receives at least 5 upvotes, it is added to our development backlog. If it receives fewer votes, the issue is closed.