Skip to content
GitLab
Next
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    Projects Groups Snippets
  • Sign up now
  • Login
  • Sign in / Register
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 46,776
    • Issues 46,776
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,532
    • Merge requests 1,532
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • GitLabGitLab
  • Issues
  • #323979
Closed
Open
Issue created Mar 09, 2021 by Christen Dybenko@cdybenkoDeveloper0 of 7 checklist items completed0/7 checklist items

✨ Exp 1 - Move "Create Board" button to be more visible

Hypothesis

If we move the Create Board button out from being buried, we will increase the number of users who create a board.

Smallest thing we can do

  • Duplicate the create button (yes would be in two places)
  • Move it

Steps to validate the test

  • Get baseline stats for the current "Create New Board" selected item being clicked ideally for 3 releases
    • This can also be a backend query to validate
  • Validate with the Backend Query at the beginning and end of the release
  • Determine if we need FE tracking tags on the old and new buttons
  • Make the change in the UI and run for 2 releases
  • See if there was a positive shift
  • Roll out on project issue boards and group issue boards

What is the risk

  • Minimal except for users who may remember where it was before

Current UI

image

Proposal

Move forward with MVC A but leave the Edit where it is

Proposed UI:

Smallest MVC

All current options would remain in the board switcher, and we would make the following changes:

💡 Inside of Boards:

MVC A MVC A +
MVC_A__Small MVC_A__Medium
Relocate the Edit board button next to the title and shorten the label to Edit. Also add a New button next to Edit. Everything in MVC A plus convert the Maximize action into an overflow menu with some of the global boards actions in it.

💡 Outside of Boards:

MVC C
Add a New issue board option within the New dropdown in the GitLab header when in a project. There could also be a New epic board when in a group. This would overlay the Create board modal wherever the user is located, and navigate the user to their new board once created.

🎨 Explorations here

Edited Nov 12, 2021 by Christen Dybenko
Assignee
Assign to
Time tracking