Skip to content
This repository has been archived by the owner on Dec 14, 2021. It is now read-only.

Spike: Investigate autofill issues post-v1.6.3 #1108

Open
sandysage opened this issue Nov 1, 2019 · 2 comments
Open

Spike: Investigate autofill issues post-v1.6.3 #1108

sandysage opened this issue Nov 1, 2019 · 2 comments
Assignees
@kaylagalway
Labels
effort-M Expected to take a week for engineering to complete. task Issue describes a task that needs to be completed but is not a defect or enhancement in itself.

Comments

@sandysage
Copy link

This is a child issue of #1070

Goal: create the sub-tasks for #1070
@sandysage sandysage added the task Issue describes a task that needs to be completed but is not a defect or enhancement in itself. label Nov 1, 2019
@marniepw marniepw changed the title Investigate autofill issues post-v1.6.3 Spike: Investigate autofill issues post-v1.6.3 Nov 1, 2019
@ddurst
Copy link

ddurst commented Nov 12, 2019

See also #1116.

@kaylagalway kaylagalway self-assigned this Nov 15, 2019
@marniepw marniepw added the effort-M Expected to take a week for engineering to complete. label Nov 15, 2019
@eliserichards eliserichards mentioned this issue Nov 26, 2019
Closed
@kaylagalway
Copy link
Contributor

New ticket created to resolve autofill issues: #1198

@st3fan st3fan closed this as completed Jan 27, 2021
@st3fan st3fan reopened this Feb 1, 2021
@st3fan st3fan removed the archived label Feb 1, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@kaylagalway kaylagalway

Labels
effort-M Expected to take a week for engineering to complete. task Issue describes a task that needs to be completed but is not a defect or enhancement in itself.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@st3fan @ddurst @sandysage @kaylagalway @marniepw