DAST: Differentiate between the "edit" and "change" profile actions (configuration)

Insight

On the updated DAST configuration pages for CI/CD and On-demand (to be implemented), users found the “edit” and “change” profile actions to be ambiguous and redundant.

Supporting evidence

Some participants found the “change X profile” and the “edit” button on the selected profile cards to be redundant, and slightly ambiguous (edit and change are loose synonyms and may be hard to differentiate).

User quotes:

Well, actually I think it's a little bit confusing because I could notice two options to edit the scanner profile card... it's a little bit redundant... I expected something inside that other option (drawer), to be honest.

...the pencil (icon) also could be interpreted, in this case, as something we would use to change the profile, but we have a specific button for that. So probably to be a little more clear on that distinction between the two actions.

• Dovetail Insight (Note: insight located halfway down page)

Action

1. Immediate action: A tooltip should be added to the "edit" button informing users that the action is to "Edit profile".
2. Additional actions:
   1. Option 1: Conduct additional research to after adding the tooltip suggested in the "immediate action" point (above) to determine if the point of confusion still exists.
   2. Option 2: Explore ways to track users' workflow and quantify the usage of each action. Monitor usage for a set period of time. This data should help determine how each action is being used. For example:
      • Do users select the "edit" button without making any changes to the profile?
        • if so, the problem may still be an issue
        • if not, the problem may not be a concern.
      • Do users select the "change X profile" action and immediately select the "edit" button
        • if so, the problem may still be an issue
        • if not, the problem may not be a concern.

Resources

• 🕊 Dovetail project
• 🔍 Research issue 1
• 🔍 Research issue 1

Tasks

• Assign this issue to the appropriate Product Manager, Product Designer, or UX Researcher.
• Add the appropriate Group (such as ~"group::source code") label to the issue. This helps identify and track actionable insights at the group level.
• Link this issue back to the original research issue in the GitLab UX Research project and the Dovetail project.
• Adjust confidentiality of this issue if applicable