DiscordJS API Version 13 requires NodeJS 16.6 or higher
https://discordjs.guide/additional-info/changes-in-v13.html#before-you-start

I would like to update my discord bots to discordJS v13. :)

Bring your Mattermost version up to date so that all features work on the Mattermost Android app and the app stops throwing a warning that the server version is out of date and not supported.

For automating Node.js setup it should be possible to set Node.js settings, like Document root , Application Startup File and variables without Plesk GUI.

It would be great to be able to control the rules that are currently not mentioned in the GUI of the Plesk Firewall extension. Perhaps, some "Advanced options" menu could be added there, for example to tweak the policies that applied initially(these are not showing in the GUI)

Actually 2 step is supported only for admin account.
Please implement also for customers.
https://talk.plesk.com/threads/google-authenticator-for-plesk-clients-query.362201/

It would be useful to add an feature of providing access to Imunify360 to particular customers so only them can manage it

Please add an option to deploy the tagging server for Google Tag Manager - this will allow to direct requests to the Plesk server instead of analytics.google.com.

Possibility of the extension "Mail Log Browser" show the logs to users

Starting from Plesk Onyx 17.8, support of the extensions protected by ionCube was stopped and now it's possible to get extension encoded only on Plesk RnD side and only when publishing it.

This way Plesk reseller cannot test it on clients' servers without exposing a source code.

The Mail Importing option from the Site Import is located at main Dashbord tab and not at Mail tab.
It would be more convenient to have it on both tabs.

Implement the functionality to add attachments to calendar items and invitations on mailboxes added via ActiveSync in Plesk Premium Email extension. Right now the button to add attachment to calendar and invitations is greyed out.

Please add Docker support for CloudLinux as currently it is possible to manage remote nodes only

Currently in SSL It! extension the option is "Include a "www" subdomain for the domain and each selected alias". In that way the Let's Encrypt limit will take effect if many aliases exist in Plesk for domain.

For example, it is required to protect example.com, www.example.com and 50 aliases. In that way Let's encrypt will protect example.com, www.example.com and 100 aliases (50 without www and 50 with WWW) and it will hit the Let's Encrypt Limit.

In some cases, it is required to change/manage settings in Watchdog (for example Preferences in Watchdog) for a great number of servers. For now, it is possible only from Plesk GUI which in the scope of about 100 servers will become a great deal to do. So it would be much convenient to be able to manage these settings with command through CLI.

Currently, if you disable 2FA and enable it again for the same account, the same secret is used (from psa db). That is a security risk because if 2FA was disabled due to the fact that a phone was lost. The next time 2FA is enabled for the same account a new secret should be generated. Otherwise, the lost phone still will be able to generate a valid code.

Implement this feature to be default behaviour or at least add a button "regenerate secret".

Related links:
https://talk.plesk.com/threads/how-to-disable-google-multi-factor-authentication-in-mysql.312675/

https://support.plesk.com/hc/en-us/articles/213407229-Cannot-disable-Multi-Factor-Authentication-for-a-customer-in-Google-Authenticator-in-Plesk

The domain validation for letsencrpypt for wildcard domains uses a TXT-record (acme-challenge.<YOURDOMAIN>).
This record is set by plesk on the local dns server, but it is not synchronized to our (the official) nameservers for a domain which is using the domainconnect extension. So the validation will fail, or the customer have to set this record manually every few months, when a revalidation is required.

Can domainconnect be improved to synchronize this record?

For example, it would be great to have a Customer John Doe that has only access to the SEO Toolkit extension.

Disable root access for the SSH Terminal extension only for additional admin users

Currently "Site Import" ext only supports username and password for SSH/FTP. If the source server doesn't support password SSH auth then it is not possible to import a website via SSH. Can the SSH Key auth option be added?

I would list to block all plugins and themes and have a whitelist of allowed plugins and themes. Currently there is only a blocklist for plugins.