We love feedback from you on our products and the problems in your daily work that you would like us to solve. Please describe the challenge you're encountering and your desired outcome. Be as detailed as possible.
For technical issues or bugs please head to Support or our Developer Community. You can assign up to 20 votes in total. Thank you for your feedback.
Status explanation: 'Future Consideration' = Continuing to collect further feedback, not planned at this time. 'Investigating' = Prioritized for deeper customer and feasibility investigations ahead of planning development.
I regularly use PaaS Portal for routine tasks in the Production environment, including DB exports, CDN cache flushes, and application log monitoring.
When I click on the Troubleshoot tab, then the first item that appears is the "Restart Site" section. Because this section looks so similar to the other three sections, and it is right at the top of the list, and I may be in a hurry, sometimes I nearly end up clicking the button to restart Production instead of doing one of the other tasks in Production. This is dangerous because it could cause Production down-time.
To minimise this risk, I'm wondering if you could consider making a few UX tweaks to this section of the PaaS Portal? Some suggestions I have are: * Move the restart site section to the bottom of the troubleshoot section so users only see it if they're specifically looking for it * Add some red colouring to the restart site section to make it clear that it is dangerous (since it can cause down-time). Maybe either recolour the whole section red or add a red banner within the section with a warning message stating that it can cause down-time. * Change the colour of the Restart Web App button to red * In the confirmation popup that appears after clicking the Restart Web App button, change the text of the "OK" button to "Restart", and change the button colour to red