Mobile/Projects/Firefox Accounts with Sync 1.1 integration

Last updated: 2014/02/13

Goals

The goal of this MVP release is primarily to provide an easy way for users to replicate their Firefox browser experience across any desktop, mobile phone or tablet screen. Broken down, this includes:

• Introducing "Firefox Account" to Android users
• Providing a much-improved mechanism for sign-up and sign-in to a functional sync experience
  • Objective: reduce barrier to entry to sign-up to use sync functionality
  • Objective: reduce number of failed attempts in setting up the account
• Utilise the existing sync service as the first valuable service attached to Firefox Accounts

The underlying tactics to achieve these goals are to:

• Integrate Firefox Accounts with the Current, Existing Sync (v 1.1) service
• Improve the sign-up and sign-in flow for sync via Firefox Accounts (username & password)
• Promote sync in-product and in product marketing materials
• A strong push to target only one flag day (user intervention)
  • Applicable for current users of sync and new users of Firefox Accounts integrated with current sync
  • This may not be entirely possible, but user intervention should be mitigated as much as possible to reduce barriers to further necessary migrations in the future

Non-goals

• Simultaneous syncing across existing sync account with Firefox Account
• No support in syncing over reading lists or any home page management
• No support for syncing add-ons between Desktop and Firefox for Android
• No support for syncing of FxOS data types (including browser information)
• No support for syncing Marketplace data types
• No explicit UX in Firefox for Windows 8 Touch (metro) - only classic Desktop will contain the UX for Firefox Account and Sync management

MVP - requirements

General

• [ON TRACK] Users can create a Firefox Account
• [ON TRACK] Users can delete their Firefox Account
• [ON TRACK] Firefox Account will enable the current Sync (v1.1) service, and the new Sync (v1.5) service? <== rnewman
• [ON TRACK] Users can sign in to their Firefox Account
• [ON TRACK] Users can sign out of their Firefox Account
• No support for federated accounts (although it is understood persona may be leveraged) <= is this true? I thought we want the new, non-persona protocol because we want accounts to be federated
• Current sync functionality must be supported, with the following being must-haves:
  • [ON TRACK] Bookmarks must be synced, with no requirement to manage bookmarks from the non-originating
  • [ON TRACK] History must be synced (to make the awesomebar relevant) using the current sync algorithm for number of days we sync <== Is this what we are doing?
  • [ON TRACK] Passwords must be synced to make the mobile experience that much tighter
  • [ON TRACK] Security standards must be adhered to in order to protect my saved passwords during syncing <== is there anything to note, here?
  • Add-ons must be synced between desktop machines only <== when do we think addons will be in scope or will they ever?
• 'Clearing Private Data' in the Settings menu results in current, existing behaviour (which we all know is confusing and convoluted, but we don't have agreement on expected behaviour)<== what's the latest on this
• [ON TRACK] 'Sync' as a name remains unchanged in the UI or corresponding materials

Set-up & Account Management

• When a user first installs Firefox, a prompt will be presented to create a Firefox Account to enable Sync
• [ON TRACK] Creation of a Firefox Account is via username (email address) and password
• [ON TRACK] COPPA requirements when creating a Firefox Account must be adhered to within the creation flow
• [ON TRACK] Present to the user what data will be synced and how this relates to their Firefox experience
  • [PROPOSED]Includes messaging what 'history' really means to the user and what benefit syncing history provides
  • [ON TRACK] Provide an option for which sync data types can be synced before the initial sync begins, applied to the Firefox Account level and not on a per-device level
  • https://wiki.mozilla.org/User_Services/Sync/Datatype_Selection_Fx29
• [ON TRACK] Users must not be forced to set up a Firefox Account if they either wish to defer the setup experience or never sign up at all. In this case, the user must be able to continue using the browser as expected, but without any benefits to having a Firefox Account
  • This also means the user will not be able to benefit from sync - if a user wishes to set up sync, they can only do so via a Firefox Account come the introduction of Firefox Accounts
• [ON TRACK] Users with an existing current Sync account (2+ devices attached to existing sync) must still be able to continue using their sync account using their existing connected devices for a transition period (minimum 3 months / 2 releases from when outbound communication has begun) <== do we have a transition plan?
• [PROPOSED] Users with an existing current Sync account (2+ devices attached to existing sync) should have a link somewhere that they can follow to explain what Firefox Accounts is and that it will be 'coming soon', given that upsell / migration will not be available to them until Fx30 <== how is this manifested? SUMO?
• [ON TRACK] Users must be able to change their Firefox Account passwords

elan placeholder

• Users must be able to reset their Firefox Account passwords
• For users who have not signed up to Firefox Account upon initial install, they may be notified or prompted to set one up in order to enable Sync
• For users who have not signed up to Firefox Account upon initial install, they must be able to initiate and complete the process from somewhere in the Settings menu
• For users who do not have an existing sync account in Fx 29, be able to present a snippet in the promo banner advertizing and linking to the FxA account flow to enable sync
• For users who have not signed up to Firefox Account or have existing sync enabled, present the ability to create an account to enable sync from the 'sync tabs' panel. NB - this is a nice-to-have in Fx 29.

Existing sync

• By setting up Firefox Account on a desktop or Android device, users expect the sync experience to propagate across all attached instances where Firefox Account signed-in and used; including bookmarks, history (awesomebar results), passwords, ability to send open tabs, add-ons [between desktop instances only]
• Frequency of syncing should remain the same when we transition to the new account creation model

Detaching Sync

• If a user wants to disable or delete their Firefox Account from a particular desktop or Android device, data previously synced should still remain on other instances where Firefox Account is active
• If a user wants to disable or delete their Firefox Account from a particular desktop or Android device, data should be preserved locally so that 'sync' stops, but the browser's current behaviour does not change from when sync stopped

Security/Encryption

• It is expected that synced data is encrypted securely along with their Firefox Account password
• Security defaults should be the same as per existing Sync 1.1 logic, with higher-level security options available
  • Expected: all user data currently irrecoverable

Performance & Stability

• In the event of service interruption to Sync, this must have no impact with current use of the browser
• In the event of service interruption, all data that should be synced will sync once service is restored in a way that is seamless to the user and without degradation to browser usage

Migration

• We want to encourage existing Sync users to migrate to a Firefox Account, without harming the experience of existing users (defined as those who have 2+ devices attached to an existing sync account) who aren't ready to move for a minimum period of 3 months from when outbound communication has begun.
• There must be overlapping support for current sync accounts who haven't signed up to Firefox Account and to the new Firefox Account & sync v1.1 for a minimum period of 3 months from when outbound communication has begun

• Wiki for migration information: https://wiki.mozilla.org/User_Services/Sync/Transition_To_FxA_Sync

Firefox for Android MVP - contextual user stories

NB: [AC] = acceptance criteria

Set-up & Account Management

• As a user, I want the option of setting up a new Firefox Account when I first install Firefox, so I can sync my browser data between my devices.
  • AC 1.
    • A new user installing Firefox for Android for the first time, there is at least one obvious entry point for setting up a Firefox Account that allows me to enable sync (whether from the promo banner or settings menu)
• As a user, I want a way to clearly understand what data Sync is actually Syncing, what that data means in terms of my browser functionality, and what happens to that data when I have logged out of my Firefox Account.
  • AC 1.
    • Well worded messaging around the relevance of 'history' is explained or reworded to better reflect the benefit (which is consolidating awesomebar results regardless of the screen used to visit a website)
  • AC 2.
    • Messaging to inform the user prior to starting the initial sync to ensure 'no surprises'
• As a user, I want to set up a Firefox Account using an email address and password of my choice, so I am not required to use any particular third-party sign-in service - I am comfortable using an email address of my choice for this purpose.
  • AC 1.
    • User can chose to use an email address of their choice
  • AC 2.
    • User can chose whatever password of choice, provided it adheres to the security standard we wish to employ (password strength rules)
  • AC 3.
    • If the password chosen does not adhere to Mozilla's password strength rules, messaging must be presented to the user clearly indicating the rules and allow them to try again
• As a user, I don't want to be forced to create a Firefox Account when I first start using Firefox, so I can start using the browser as quickly as possible once I've downloaded and installed it.
  • AC 1.
    • In the FxA setup flow, users must be able to cancel out of the flow
  • AC 2.
    • If a user does not chose to initiate or complete the FxA creation flow, the user can still use the browser without any change in browser functionality EXCEPT that they cannot enable sync
• As a user, I want all of my data (history, bookmarks, etc.) to be saved on my local machine whether or not I've set up a Firefox Account, so I am still able to build up a collection of data and personalize my Firefox experience over time.
  • AC 1.
    • No loss in current browser functionality in terms of storing history, passwords, etc whether a FxA has been created or not
• As a user, I want to be able to change the password for my Firefox Account data from any device that allows me to sign into my Firefox Account, so if someone does steal my laptop or other mobile device they won't be able to access any new data that is added to my Sync Account, even though they will be able to access the data that had been previously synced and is local on the device.
  • AC 1.
    • There is an intuitive flow in the Settings / Sync menu that allows a user to change their FxA password
  • AC 2.
    • Once password change, other screens logged into FxA must prompt the user at the earliest possible stage to enter the new password
  • AC 3.
    • Although current synced data cannot be undone, new data cannot be synced to other screens logged into FxA until the new password has been entered
• As a user, I want to be able to reset the password for my Firefox Account data from any device that allows me to sign into my Firefox Account, so I can continue using my Firefox Account even if I have forgotten my password.
  • AC 1.
    • There is an intuitive flow in the Settings / Sync menu that allows a user to reset their FxA password
  • AC 2.
    • Once password change, other screens logged into FxA must prompt the user at the earliest possible stage to enter the new password
  • AC 3.
    • Although current synced data cannot be undone, new data cannot be synced to other screens logged into FxA until the new password has been entered
• As a user, I want to be prompted to create a Firefox Account when I first install my browser, but I want it to be easy to dismiss with a prompt to dismiss either forever (so I don't get bothered again), or to be reminded again later. I also want it to be very easy to get more details about what a Firefox Account is and why I would want it before I go through the process of creating one.
  • AC 1.
    • If there is a first-run experience to create a FxA upon initial browser install, users must be able to either complete the flow or dismiss the flow with no adverse effect in browser functionality EXCEPT that they cannot enable sync
  • AC 2.
    • Users can either be reminded later to set up a FxA or be able to dismiss the prompt forever
  • AC 3.
    • Any time a user is presented with a prompt to set up a FxA [in order to enable sync], clear and concise messaging must be provided as to the benefit of doing so before creating the account
• As a user, I want to be able to go into a settings menu to create my Firefox Account [to enable sync], so that I can set up it up in my own time.
  • AC 1.
    • Users without an existing sync account can go into the Settings / Sync menu to create a FxA in order to enable sync
• As a product manager, I want to use the 'promo banner' real estate on the about:home default page to advertize the ability to create a Firefox Account to enable sync for new users only (not visible to users with an existing sync account) in Fx 29 as a real ideal way of spreading the message in-product.
  • AC 1.
    • A snippet message can be displayed to a specific set of users (by geography, channel, Fx release) to encourage them to set up a FxA to enable sync
  • AC 2.
    • Tapping on the promo snippet takes the user to a FxA creation flow to enable sync
  • AC 3.
    • Existing sync users do not get this promo banner
  • AC 4.
    • Users who have created a FxA to enable sync do not get this promo snippet again
• As a user, I want to be able to go into the 'sync tab' panel and be presented with an option to create my Firefox Account to enable sync to serve as another entry point a user may stumble upon. NB this is a nice-to-have for Fx 29, otherwise can be moved to Fx 30.
  • AC 1.
    • When a user taps the 'sync tab' in the tab tray, concise & clear messaging is provided about the benefits of creating a FxA to enable sync with a link taking the user to the account creation flow
• As a user, my only option to enable sync is to create a FxA from Fx29 onwards.
  • AC 1.
    • Current existing sync sign-up and device pairing is no longer supported from Fx29
  • AC 2.
    • The only way to enable sync is by completing the FxA creation flow for new users
• As a user, I want to be able to verify my email address and my desire to set up a Firefox Account by clicking a link in the verification email I received from Firefox
  • AC 1.
    • Users can open the verification email after completing the appropriate steps in the FxA creation flow
  • AC 2.
    • Users can click a link in the email to verify their email address
• As a user, I want the option to review the ToS and Privacy Policy so that I can make sure I’m comfortable providing my information to Mozilla.
  • AC 1.
    • Users can link to the ToS from the “Create Account” page
  • AC 2.
    • Users can link to the Privacy Policy form the “Create Account” page
  • AC 3.
    • Both the ToS and PP will open in a mobile-friendly format
  • AC 4.
    • A user may accept or decline the ToS and/or PP
  • AC 5.
    • If a user declines the FxA creation flow is stopped
  • AC 6.
    • If a user accepts, the FxA creation flow continues
• As a user I want to tell Firefox how old I am so that I can be cleared for COPPA restricted activities
  • AC 1.
    • Users will be asked to provide their year of birth on the account set up page where they enter their email address and password
  • AC 2.
    • If a user enters a year that indicates their age is less than 13 years old on the day they attempt to set up an accountm she will be denied a Firefox Account
  • AC 3.
    • If a user enters a year that indicates their age is at least 13 years old on the day they attempt to set up an account, she will be granted a Firefox Account

Core existing sync user stories

• As a user, I want to be able to pick up any new device and replicate my Firefox experience so I don't have to repeat a bunch of work I've already done on another device or computer.
  • AC 1.
    • Any data that is supported by current sync must be supported by FxA+Sync1.1
  • AC 2.
    • Screens I have signed in to FxA with the same credentials are all attached to the same sync profile so that the data is replicated across all linked machines
  • AC 3.
    • Users cannot detect any performance differences between current sync and FxA+Sync1.1
• As a user with several devices, I want my core Firefox experience to be available on all devices, so I don't have to spend a lot of time rebuilding my top sites & awesome screen experience.
  • AC 1.
    • History is synced by default, unless otherwise customized 'off' during FxA & Sync setup flow
  • AC 2.
    • No perceptible change in syncing SLA from current sync to FxA+Sync1.1
• As a user, if I have typed in and stored a password in Firefox on one device or computer, I don't want to have to type and store that password again on any of my other devices so my web accounts & passwords are magically available on all of my devices (especially important so I don't make typing mistakes on my mobile and become frustrated!).
  • AC 1.
    • In the setup flow, concise & clear messaging is provided about the benefits of syncing stored website passwords
  • AC 2.
    • Passwords are synced by default, unless otherwise customized 'off' during FxA & Sync setup flow
• As a user, I want the option of syncing my tabs from other devices so I can pick up where I left off when I switch to another device.
  • AC 1.
    • No change in current sync functionality in that users can send tabs between screens logged into the user's FxA
• As a user, I want all of my bookmarks to be synced across my devices, although I don't expect full bookmark management tools on mobile devices. Any bookmarks I create while on mobile devices should be put into a single "Mobile" (or similar) folder which is then synced. Desktop bookmark organization & behaviour should not change and vice versa.
  • AC 1.
    • Bookmarks are synced by default, unless otherwise customized 'off' during FxA & Sync setup flow
  • AC 2.
    • Users cannot manage (ie delete, remove, rename) bookmarks that were created by another device
  • AC 3.
    • Users can access bookmarks from another FxA device from a folder
• As a user, I want to customize my sync preferences so I can choose what data to share across my screens for syncing so I have control of the data I am sending to the cloud.
  • AC 1.
    • Preferences can be accessed in the Settings / Sync menu
  • AC 2.
    • Preferences are global and not local to the device where applicable
  • AC 3.
    • 'add-ons' and browser 'preferences' can only be shared across desktop clients and therefore not appear in the mobile settings preferences list

Detaching Sync

• As a user, I want to be able to stop Syncing to preserve data costs on my mobile, but be able to preserve the ability to sync when I resume syncing again.
  • AC 1.
    • In the Settings / Sync menu, users must have the ability to turn off sync either by expressly 'turn off sync' or 'sign out of FxA'
  • AC 2.
    • In the Settings / Sync menu, users must have the ability to resume sync either by expressly 'turn on sync' or 'sign in to FxA'

Security/Encryption

• As a user, I expect Firefox Sync to securely encrypt all my Firefox server data with my Firefox Account password.
  • AC 1.
    • Data is encrypted as per current security standards
  • AC 2.
    • Data management must adhere to Mozilla security & privacy policies

Performance & Stability

• As a user, in the event of Sync service interruptions, I expect to be able to use my browser and previously-synced local data as normal, even if Firefox cannot access the Sync servers for an extended period of time.
  • AC 1.
    • Users must detect no change in browser behaviour EXCEPT that sync is not syncing
  • AC 2.
    • Users must detect no change to browser performance when sync service is resumed and the backlog of sync data is being processed

Migration

• As a user who currently has an existing sync account with 2+ devices attached to it, I cannot migrate to FxA+Sync1.1 using the standard points of entry in Fx29 but I can find out what's going on.
  • AC 1.
    • SUMO article is written about the migration of existing sync users
  • AC 2.
    • Release notes are written about the migration of existing sync users
  • AC 3.
    • A link is available in-product (Settings / Sync) that points to an article or information about the migration of existing sync users
• As a user who currently has an existing sync account with 2+ devices attached to it, I can migrate to FxA+Sync1.1 using the standard points of entry from Fx30 onwards.
  • AC 1.
    • FxA creation points of entry must all support migration existing sync users through the FxA flow
  • AC 2.
    • Current sync account is moved over to the new FxA system and the user cannot access their 'old sync account' any more
  • AC 3.
    • Once migrated, users can only manage their sync account via FxA and not through any old sync methods
• As a user who currently has an existing sync account with 2+ devices attached to it, I expect my current sync functionality to behave as-is for a minimum of 3 months from when outbound communication about the service EOL has started (expected to begin in Fx 30)
  • AC 1.
    • Outbound comms plan prepared and in place about EOL-ing existing sync and replacing it with FxA+Sync1.1
  • AC 2.
    • EOL will not happen for a minimum of 3 months (2 release cycles) from when outbound comms actively have begun
  • AC 3.
    • Once EOL hits, existing users will not be able to access their sync unless they migrate to FxA

Quality Criteria for Fx29

• No migration

Tickets

P1

Note: it would be better for this query to be just P1 tickets blocking the meta bug 799726, but the Bugzilla query doesn't compute the transitive closure of the blocking set so some tickets are missed.

No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);

Tracking

No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);

Resolved

Full Query

ID	Priority	Summary	Status	Assigned to
799729	P2	Generalize BaseResource authentication to support Basic-Auth, BrowserID, and HMAC	RESOLVED	Nick Alexander :nalexander [he/him]
799732	P1	Implement TokenServerClient for interacting with token server service	RESOLVED	Nick Alexander :nalexander [he/him]
799734	P1	Implement Java BrowserID crypto library for Android services projects	RESOLVED	Nick Alexander :nalexander [he/him]
808813	P1	Implement Firefox Account Android account type	RESOLVED	Nick Alexander :nalexander [he/him]
809211	P4	Implement UI for updating credentials of an existing FxAccount	RESOLVED
892025	--	Implement Android client for PICL Authentication/Keyserver	RESOLVED	Nick Alexander :nalexander [he/him]
899217	--	First version of Firefox Account sign up/sign in screen on Android	VERIFIED	Nick Alexander :nalexander [he/him]
905433	--	Implement Android Java client side key stretching library	RESOLVED
905435	--	Connect UI and backend pieces to create Android Firefox Account objects	RESOLVED
905438	--	Implement Android SyncAdapter class that syncs with Sync 1.1 against Firefox Account object	RESOLVED	Richard Newman [:rnewman]
915312	P2	Ship minimal PBKDF2-SHA256 native library for Android	RESOLVED	Michael Comella (:mcomella) [NI reported issues only: ex-Mozilla]
951264	--	COPPA support for Firefox Accounts on Android	VERIFIED	Nick Alexander :nalexander [he/him]
951304	--	Implement Android native Firefox Account sign up/sign in UI	RESOLVED	Nick Alexander :nalexander [he/him]
955808	--	Java (Android) Firefox Account client that speaks "onepw" protocol	RESOLVED	Nick Alexander :nalexander [he/him]
956444	P1	Handle Sync storage deprecation indicators for Firefox Accounts migration	VERIFIED	Nick Alexander :nalexander [he/him]
956839	P1	Implement Android native Firefox Account status UI	RESOLVED	Nick Alexander :nalexander [he/him]
956844	--	Update Android FxSyncAdapter to use new "onepw" protocol login flow	RESOLVED	Nick Alexander :nalexander [he/him]
957845	P1	[meta] Deprecate Android Sync account type in Fennec	RESOLVED
957872	--	Remove SyncAdapters for all but the main Fennec ContentProvider	VERIFIED	Richard Newman [:rnewman]
957894	P1	Update account pickling code for Firefox Account	RESOLVED	Michael Comella (:mcomella) [NI reported issues only: ex-Mozilla]
958889	P1	Make Fennec "Synced Tabs" tray display entry point to Firefox Account + Sync when user has no existing accounts	VERIFIED	Michael Comella (:mcomella) [NI reported issues only: ex-Mozilla]
958891	--	Make Fennec about:home advertise Firefox Accounts + Sync banner	RESOLVED	:Margaret Leibovic
959032	P2	Support "409 Conflict" errors from sync1.5 storage servers	RESOLVED
959033	P3	Don't send X-Confirm-Delete header	RESOLVED	kimsaehun
959774	--	ToS and Privacy Notice links for FxA	VERIFIED	Richard Newman [:rnewman]
959784	--	Submitting empty create account form displays Java error	VERIFIED	Nick Alexander :nalexander [he/him]
959790	--	"Show password" button does not toggle password display	VERIFIED
959794	--	Validate password length	VERIFIED
959915	P1	Adapt FxA token server client to include X-Client-State header	RESOLVED	Richard Newman [:rnewman]
960324	--	Use "BrowserID" in tokenserver authz header, not "Browser-ID"	VERIFIED	Ryan Kelly [:rfkelly]
961135	--	Firefox Accounts Setup (Account Creation) - needs a larger year range	VERIFIED
962126	P1	Strip debug logging and PII leaks from Android Firefox Accounts before merge to Aurora	RESOLVED	Nick Alexander :nalexander [he/him]
962644	P1	Firefox Accounts (Entry) - Settings → Sync, replace old entry with new entry	VERIFIED	Richard Newman [:rnewman]
963062	--	Firefox accounts (Android) - Can't confirm emails using Firefox mobile - the confirmation links are broken	VERIFIED
963160	P1	Firefox Accounts (Sign-Up/Sign-In) Use normalized email addresses where appropriate	VERIFIED	Nick Alexander :nalexander [he/him]
963424	P1	Use token server-provided cluster URL	RESOLVED	Richard Newman [:rnewman]
963429	--	Use current dev server URLs	RESOLVED	Nick Alexander :nalexander [he/him]
963448	P1	Add "1.5" to FxA client records	RESOLVED	Richard Newman [:rnewman]
963618	P1	Verify that changes for FxA do not affect Sync 1.1	RESOLVED
963667	P1	Use production Firefox Accounts endpoints in Fennec	RESOLVED	Nick Alexander :nalexander [he/him]
963833	--	[meta] Remaining work for Android native Firefox Account sign up/sign in UI	RESOLVED
964863	--	[meta] Linkifying	RESOLVED	Richard Newman [:rnewman]
965038	--	Styling for links	VERIFIED	Richard Newman [:rnewman]
965061	--	Handle Back presses in FxA setup activity	RESOLVED
965064	--	Back out non-native about:accounts	RESOLVED	Richard Newman [:rnewman]
965366	P1	Make Firefox Account's StatusActivity checkboxes "live"	RESOLVED	Nick Alexander :nalexander [he/him]
965367	P1	Implement "Choose what to sync" check box and dialog for Firefox Account CreateAccount activity	VERIFIED	Nick Alexander :nalexander [he/him]
965376	P1	Update final copy for Android Firefox Accounts landing	VERIFIED	Nick Alexander :nalexander [he/him]
965867	P1	Update final URLs for Android Firefox Accounts landing	VERIFIED	Nick Alexander :nalexander [he/him]
965910	P3	Sync intermittently failing with prod token server	VERIFIED
966104	P2	Add statusChangeListener to FxA status screen	RESOLVED	Nick Alexander :nalexander [he/him]
966105	P2	Automatically transition from verification email screen to the verified screen	RESOLVED
966106	--	Detect existing accounts during account creation, and offer to sign in	VERIFIED	Richard Newman [:rnewman]
966174	--	Skip straight back over Get Started when successfully setting up FxA	VERIFIED	Richard Newman [:rnewman]
967831	--	Setup flow doesn't offer reset/merge options	RESOLVED
969227	--	Handle X-Backoff headers	RESOLVED	Richard Newman [:rnewman]
969672	P1	Handle declined engines in meta/global	RESOLVED	Richard Newman [:rnewman]
972051	P1	Dismiss "Tap to sign in" notification when a sync succeeds	VERIFIED	Nick Alexander :nalexander [he/him]

58 Total; 0 Open (0%); 36 Resolved (62.07%); 22 Verified (37.93%);

Incoming

No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);