This issue will be used to document the requirements needed to update tracking analytics in to the import/export work flows. We want to have quantitative data to guide our feature growth in the area of import / export as it pertains to groups and project creation.
Key tracked data points
Entry
Exit
tabs
cancel
continue
templates
click backs? (user makes a mistake and goes back to the origin?)
click through flow? (is there a standard flow)
What usage do we see for each one of the importers?
How many users use export/import for backups vs one-time data migration? (this would be important to know before we replace the file-based export/import with a direct migration solution)
External research
What other importers would be used if they existed (eg.JIRA)?
How many self-hosted customers want to move to .com?
History
From previous issues #25647 there has been some tracking done as far as new project creation. @matejlatin mentions in this issue the majority of users are creating blank projects. This data is quite old, but it can provide a starting point to build further tracking.
@jhyson@lmcandrew@dennis@georgekoltsov@dmoraBerlin@kassio
I would like to identify important questions that we would like to answer in order to have a better understanding of the future priorities for Category:Importers. Please provide your feedback on the list of questions above, add any questions that you might have, which are not listed above.
@hollyreynolds and I came up with some questions for JIRA importer which I think would add to the ~"group::import" project we're working on here. I added the issue to the related items and will also add those questions here, as they relate to the broader Import project.
@hdelalic these are questsion I had in relation to JIRA importer but can be expanded to other imports. They would need to be changed a bit to reflect more quantitative data.
Who wants to import from JIRA to GitLab.
Why are they importing. (For testing? Migrating to GitLab? Wanting to save a client from leaving GitLab.)
What objects do they want to import.
What do they expect to come over in an import (what is mandatory).
Do they want full/one time only import, segmented or progressive import?
What are the exceptions of import types
Will my issues be updated over time?
Will I need to start over every time? Would that cause frustration / duplication of issues?
@jeremy Just wanted to make you aware of this issue. Please contribute your insights and questions. Once we gather and prioritize all the questions, we will start looking for answers.
Not sure how to accurately measure this intent. This will probably be a guess, given the interest in issues and what customer success and sales teams are hearing.
We should definitely get the counts of all the different import actions.
@dennis I think you mentioned in a previous meeting that there was some tracking embeded currently, how every, if users had it disabled/inactive, obviously it wouldn't report. Is there any way to get any of that data?
What data do we currently have as far as usage/errors with the current importing systems that @hdelalic could start analyizing?
I spoke with @xanf about this topic briefly. He mentioned he would do some investigating. Can you update this issue on anything you found @xanf ?
Also @hdelalic@xanf can we expand on points of data to be tracked. I added a few, but I think someone with a stronger knowledge of tracking and front end dev might have more insight.
@hdelalic Is there any value in tracking new users (first-time use) vs returning users using Import?
@jhyson You shared a chart showing imports via API vs the UI not too long ago. That info probably would be valuable to have in the Importer dashboard. What do you think and how "easy" would it be to do so?
@hdelalic Perhaps tracking new versus existing users using the Import features isn't important to track quite yet. I'd be more curious to learn any discoverability for existing users.
I'll create an issue for surfacing the API vs UI data in the Importer dashboard.