[ANALYTICS-186] [Investigation] Normalise labelling of custom data supplier Created: 12/Aug/20  Updated: 16/Sep/20  Resolved: 15/Sep/20

Status: Closed
Project: Analytics
Component/s: None
Affects Version/s: None
Fix Version/s: 1.2

Type: Improvement Priority: Major
Reporter: Laura Delnevo Assignee: Antonín Juran
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 2.5d
Original Estimate: Not Specified

Issue Links:
duplicate
is duplicated by ANALYTICS-132 Research all dimensions/metrics from ... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Epic Link: UI/UX Dash improvements
Sprint: Add-Ons 46
Story Points: 5

 Description   

Issue

json path data is not easy to understand (what data to pick) 

Tech complexity
We bring all of analytic connector to integrate. Each of connectors (google, matomo, adobe) has different analytic structures and of course the combobox contain auto generated json path data ( $.reports.[].data.rows.[].metrics.values.... ) is quite not easy for end user.
 
 Investigation/Solution 

  • Investigate complexity to replace the combox contains json path with metrics combobox for google, adobe, matomo connectors.
  • For other custom data supplier, we can't get metrics or any so user may config the data for combobox as they want or like I do to auto generate all jsonpath from data supplier for user to evaluate data and select as they want to
  • e.g. Remove $.[*] 

Generated at Sun Feb 11 23:16:22 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.