Skip to content

Navigation proposal - Add import history to Your Work

Summary

This change is already in production ( !179752 (merged)_)_

Background

Link to epic / issue with overall feature proposal: Improve discoverability of import results (#431178)

Does this navigation proposal facilitate one of our primary JTBDs? Which job?

-> Yes, it does. As an importing user, I want to easily understand the result of the imports I run.

How does this change improve the workflow for users attempting to complete that job?

-> Button to navigate to import history page was available only on the page where the user starts an import. So to see the history of imports they would need to go as if to start another import. Also, users easily missed that button and didn't know how to navigate to page where they could see import results.

How many users will be impacted by this proposed change?

  • Limited
  • Moderate - it will affect all users that run imports, would would not be all users in general
  • All users

What is the product maturity stage of the associated feature?

  • Experimental
  • Beta - project import by Direct transfer (DT) is still in beta
  • General availability - group import by DT is in GA, as are all other importers

The import results are listed on the same page. If I needed to choose just one, it would be GA.

How often do you expect an average GitLab user (not just your target persona) to reach for this functionality?

  • Several times a day
  • Once a day
  • A few times a week
  • Once a week
  • Less than once a week

Approaches considered

Please describe the alternative designs you considered.

@jmiocene could you support me with this one please?

Justification

Provide your justification for this change. See https://handbook.gitlab.com/handbook/product/ux/navigation/ for the minimum validation we request based on the scope of access of your proposed change.

This change supports "Organize content" JTBD (as listed in https://gitlab.com/gitlab-com/www-gitlab-com/-/blob/master/data/jtbd.yml?ref_type=heads) with outcome Decrease time it takes team members to locate specific content inside the tool.

Why is this change important? -> Customers migrating GitLab resources between GL instances and/or importing resources from 3rd party providers to GitLab have to check if the items that they wanted to migrated imported correctly and fully, or not. Otherwise they cannot follow on their journey to start using GitLab or another GitLab offering.

Review checklist

Requester

  • Review the handbook page for navigation.
  • Add relevant information to the issue description detailing your proposal, including usage and business drivers.
  • List at least two other places you considered to introduce your feature.
  • Add relevant designs to the Design Management area of the issue.
  • Ensure your UI suggestion align with the Documentation Style Guide.
  • Engage Technical Writing. They can help craft a term that best describes the feature(s) you’re proposing.
  • Follow the product development workflow validation process to ensure you are solving a well understood problem and that the proposed change is understandable and non-disruptive to users. Navigation-specific research is mandatory for additions or when restructuring.
  • Engage the Foundations Product Manager for approval. The Foundations DRI (@jtucker_gl) will work with UX partners in product design, research, and technical writing, as applicable.
  • Consider whether you need to communicate the change somehow, or if you will have an interim period in the UI where your item will live in more than one place.
  • Ensure engineers are familiar with the implementation steps for navigation.

Foundations Product Manager

  • Confirm proposal has necessary information
  • Schedule design review for next milestone

Foundations Product Designer

  • Confirm Pajamas guidelines are followed
  • Confirm a11y needs are addressed
  • Confirm burden of proof supplied for stated scope of access
Edited by Magdalena Frankiewicz