Closed jeffchew closed 5 years ago
On Aug 30, Jeff-Chew commented: Speaking with Juan Leon, we may be reducing scope of this, and to only expose more generic event based data from our respective components. Will need to look through the documentation and see what we will need to do for v1.0.0.
On Sep 06, Jeff-Chew commented: @hahnrob it looks like the scope of work will need to be broken down to various components as we need to add in dynamic event triggers, so I'm breaking this up into multiple stories:
cc: @james-dow @vladislav-saling @Kenny-Lam @Anna-Wen
On Sep 10, hahnrob commented: Juan can't get the information to Jeff until the end of the week. This issue will move into sprint 18. If the analytics work is required for the ibm.com Library v1.0.0 release, the code freeze date will be affected. The topic of the release scope is included in the Sept 10 Leadership meeting agenda.
On Sep 23, Jeff-Chew commented: Based on conversations with Juan, we should do the following for this sprint:
My thought is to then set the following for v1.1.0:
Juan has shared the following spreadsheet for events to track: https://ibm.ent.box.com/s/jw44u3vh2cxg0exgjwthvk03do79iki4
cc: @linda-carotenuto @Wonil-Suh1 @Kenny-Lam @james-dow @Anna-Wen
On Sep 24, Jeff-Chew commented: Base analytics tag was added to storybook for internal testing: https://github.com/carbon-design-system/ibm-dotcom-library/pull/103
hahnrob created the following on Jun 26:
User story TBD
Additional Information
Acceptance criteria
Original issue: https://github.ibm.com/webstandards/digital-design/issues/1131