New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate all existing user() usage to element.user() #10891

Open
lannka opened this Issue Aug 11, 2017 · 5 comments

Comments

@lannka
Collaborator

lannka commented Aug 11, 2017

For #6415

@lannka lannka added this to On Deck for Next Sprint in Analytics Aug 11, 2017

@rudygalfi rudygalfi moved this from On Deck for Next Sprint to In Progress This Sprint in Analytics Aug 22, 2017

@lannka lannka changed the title from Migrate all existing user() usage to user(element) to Migrate all existing user() usage to element.user() Aug 24, 2017

@rudygalfi

This comment has been minimized.

Show comment
Hide comment
@rudygalfi

rudygalfi Aug 25, 2017

Contributor

@tiendt Just wanted to confirm: Is this closed by #10858 or is this still other tasks pending?

Contributor

rudygalfi commented Aug 25, 2017

@tiendt Just wanted to confirm: Is this closed by #10858 or is this still other tasks pending?

@tiendt

This comment has been minimized.

Show comment
Hide comment
@tiendt

tiendt Aug 25, 2017

Contributor

@rudygalfi I still have another task pending!

Contributor

tiendt commented Aug 25, 2017

@rudygalfi I still have another task pending!

@rudygalfi rudygalfi moved this from In Progress This Sprint to On Deck for Next Sprint in Analytics Aug 25, 2017

@rudygalfi rudygalfi moved this from On Deck for Next Sprint to In Progress This Sprint in Analytics Aug 25, 2017

This was referenced Aug 27, 2017

@lannka lannka assigned zhouyx and unassigned tiendt Sep 8, 2017

@lannka lannka added this to the Sprint H2 September milestone Sep 11, 2017

@rudygalfi rudygalfi moved this from In Progress This Sprint to On Deck for Next Sprint in Analytics Oct 3, 2017

@rudygalfi

This comment has been minimized.

Show comment
Hide comment
@rudygalfi

rudygalfi Oct 26, 2017

Contributor

@zhouyx I think we should schedule this soon. Do you have an estimate on the size of effort required?

Contributor

rudygalfi commented Oct 26, 2017

@zhouyx I think we should schedule this soon. Do you have an estimate on the size of effort required?

@rudygalfi rudygalfi moved this from On Deck for Next Sprint to Sprint Candidate in Analytics Oct 27, 2017

@ampprojectbot

This comment has been minimized.

Show comment
Hide comment
@ampprojectbot

ampprojectbot Jan 29, 2018

Collaborator

This issue hasn't been updated in awhile. @zhouyx Do you have any updates?

Collaborator

ampprojectbot commented Jan 29, 2018

This issue hasn't been updated in awhile. @zhouyx Do you have any updates?

@lannka

This comment has been minimized.

Show comment
Hide comment
@lannka

lannka Jan 29, 2018

Collaborator

Let's bump its priority after the AMP Conf

Collaborator

lannka commented Jan 29, 2018

Let's bump its priority after the AMP Conf

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment