Build tracking analytics into Import/Export
Proposal
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? -
What number/percentage of imports are successful/failed/partially succeded (by importer)? -
What size are the imports (by importer)? -
How long do the imports take (by importer)? -
How many users use API/command line vs UI? -
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.
Requirements
tbd
Edited by Haris Delalić