Existing GitLab for Jira setup experience

Problem to solve

As mentioned in #229542 (closed) :

The GitLab for Jira listing on the Atlassian Marketplace has a 5% rate of successful installations. This is driving very poor ratings, and we need to fix it.

In order to understand why the installation success rate is so low, I went through the process myself and documented my experience.

Walkthrough of existing flow

Related support issues (internal)

Summary: The highest friction points in the installation flow seem to be on the Configuration screen, where a namespace is required and then after a namespace has been added, it is not clear what to do next.

Recommended updates

Ordered by highest impact and lowest level of effort:

  1. Making authentication a requirement if 0 namespaces have been added, and display the current username that is logged into GitLab (#235888 (closed))
  2. Make selecting a namespace easier by exposing a list of available namespaces along with a to filter namespaces in Jira Connect App (#13020 (closed))
  3. Make it clearer on what to do next, after a user has added a namespace (#235909 (closed))
  4. Improve GitLab for Jira listing page on Atlassian Marketplace by adding clearer copy and more visuals (#229542 (closed))
  5. Improve error messages by leveraging existing GitLab UI patterns in the Jira Connect App (#13019 (closed))
  6. Improve Connect Application Documentation (#229355 (closed))
  7. Overall, simplify Jira integration/installation flow when integrating with GitLab for Jira <> Jira for GitLab (#225803)

Updated installation flow:

Edited by Libor Vanc