Code Intelligence next steps

What’s this issue all about?

After we introduce basic features for code intelligence, we'd like to:

1. find what features users would like to see next
2. find what are the most common languages used on self-managed GitLab instances

Who is the target user of the feature?

Developers who are currently using or would like to use code intelligence. Does not have to be GitLab-native code intelligence.

What questions are you trying to answer?

1. find what features users would like to see next
2. find what are the most common languages used on self-managed GitLab instances

Additional questions

What hypotheses and/or assumptions do you have?

1. Starting with a focus on popular languages from other surveys (such as Stack Overflow's 2019 dev survey) is a good start.

2. A powerful elasticsearch capability will negate the need to have code search on the code intelligence part.

What decisions will you make based on the research findings?

What's the latest milestone that the research will still be useful to you?

~13.4

Progress

• UX Researcher: Draft the survey questions.
• UX Researcher: Enter survey questions into Qualtrics.
• UX Researcher: Open a banner request issue for the documentation site. gitlab-docs#906 (closed)
  • UX Researcher: Review responses received so far. Amend survey if necessary. Advise Research Coordinator to continue recruitment.
  • UX Researcher Pay participants.
• UX Researcher, Product Manager: Synthesize the data and identify trends, resulting in insights.
• UX Researcher: Document insights in Dovetail
• UX Researcher: Update the Problem validation research issue. Link to findings in Dovetail. Unmark as confidential if applicable. Close issue.