Experience Recommendations - Secure FY20-Q4 - Security gates (responsibility): how to approve a MR

UX scorecard Part 1: video and problem explaination:

• UX Scorecard issue: #534 (closed)

Recommendations:

From part 1 UX scorecard, we identified problems, here are the details and recommended solutions:

Problem	Solution
Problem 1: In settings, there are three approvals, when creating an MR, there is only one show up. User might wonder why? And add existing rules again while during MR creation	Solution 1: The purpose is to tell the user the same info after they create MR. If after the MR created, there will be 3 approvals, during the creations of MR, there should be 3 as well. There is no need to hide some of the approvals during the MR creation.
Problem 2: There is only one approve button. When the user approves UX Check, License-Check will be automatically approved by the user. As a user, can I choose to approve only one?	Solution 2-1: instead of approving them all together, we should give user option to approve them one by one. Theoretically, there shouldn't be too many rules at the same time. So the 1 button prove-all feature shouldn't be a need. But can confirm this with research.
	Solution 2-2: Separate 'general approvals' VS 'security approvals'. This is more recommended feature compare to the previous one. Security approvals are highly related with findings below. Have a different area, make it easier for the user to review the findings and then approve the MR.
Problem 3: MR can’t be merge, because of approvals needed. But the message above says that is has been approved: It is not clear for the user, what is approved? What is not? CTA “View eligible approvers” is not clear to tell the user there are multiple approvals need to be reviewed	Solution 3: The solution here is simply changing the copies make it clear: what need approvals, what has been approved already. The collapsed list could be open by default until everything is approved.
Problem 4: There are two reasons why MR can’t be merged: conflicts and approvals. But in current status-quo, it only shows one. User might want to take the security issue as appriority instead of fixing the conflict. Why don't inform the user about the status?	Solution 4: Make the copies clear to user, the MR is blocked because of two reasons instead of only one

Experience Recommendations Checklist

Learn more about UX Scorecards

1. Add this issue to the stage group epic for the corresponding quarter's UX scorecards.
2. Brainstorm opportunities to fix or improve areas of the experience.
   • Use the findings from the Emotional Grading scale to determine areas of immediate focus. For example, if parts of the experience received a “Negative” Emotional Grade, consider addressing those first.
3. Create an issue for each recommendation and add them as related to this issue.
4. Think iteratively, and create dependencies where appropriate, remembering that sometimes the order of what we release is just as important as what we release.
   • If you need to break recommendations into phases or over multiple milestones, create multiple epics and use the Category Maturity Definitions in the title of each epic: Minimal, Viable, Complete, or Lovable.