You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
The problem is that approval gates are just that: a gate. They slow things down. They take time to open. They frustrate people who are trying to walk fast. Let's make them as smooth and easy to open as possible.
One source of frustration is that after typing in a ton of information on a chromestatus entry, each time you click an approval gate request button, you get a "survey" asking for even more information. Much of that information is already present somewhere in the body of the chromestatus entry. Other questions aren't. Some questions sound like you're agreeing to a TOS agreement: "do you promise that your change is good and right and helpful?" It's painful.
Describe the solution you'd like
Just make sure all required content is present in the body of the chromestatus entry. If there's an important piece of information that an Enterprise approver needs, ask for it in the chromestatus. Don't add new questions right at the end, right when requesting approval gates. Especially for questions for which the answer is commonly "N/A".
If something in the chromestatus is missing or needs more detail, the approver should be able to ask for that information.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
The problem is that approval gates are just that: a gate. They slow things down. They take time to open. They frustrate people who are trying to walk fast. Let's make them as smooth and easy to open as possible.
One source of frustration is that after typing in a ton of information on a chromestatus entry, each time you click an approval gate request button, you get a "survey" asking for even more information. Much of that information is already present somewhere in the body of the chromestatus entry. Other questions aren't. Some questions sound like you're agreeing to a TOS agreement: "do you promise that your change is good and right and helpful?" It's painful.
Describe the solution you'd like
Just make sure all required content is present in the body of the chromestatus entry. If there's an important piece of information that an Enterprise approver needs, ask for it in the chromestatus. Don't add new questions right at the end, right when requesting approval gates. Especially for questions for which the answer is commonly "N/A".
If something in the chromestatus is missing or needs more detail, the approver should be able to ask for that information.
The text was updated successfully, but these errors were encountered: