Issue: [User Story] Ask and handle location permission 
Repositório: multei/web
Data: 04/05/2020
Status: Fechado

Closed
21 tasks done
[User Story] Ask and handle location permission
#181
jimmyandrade opened this issue on May 4, 2020 · 0 comments
Comments
@jimmyandrade
Member
jimmyandrade commented on May 4, 2020 • 
User story
As a user who is creating a parking report
I want to accept revealing my address by GPS on a map
So that authorities can find where the parking report is taking place

Business context
In order to submit a report with enough information for authorities to eventually take action, the localization of the user is necessary. Without this information, it would be difficult to identify where the car is parked, even with car plate information. In order to know the car location, we need to ask for their permission to use GPS.

A clear and concise description about the business context

Describe alternatives you've considered
Offering the user a field to type their address.

In scope
Show button "Permitir uso da localização".
Associate the button with the API Google Maps to show the car position.

Out of scope
Showing the address data on the screen as a map (#183).
Obtaining confirmation from the user regarding their address (#208).

Acceptance Criteria
 1. Obtaining authorization and delegating to API Google Maps
Given the user has already selected a parking photo,
When the user clicks on "Permitir uso da localização",
Then Multei app shows the text "Obtendo localização" and the maps with location.

 2. Persist coordinates on database
Given the user has already allowed the permission,
When the user clicks on the 'Finalizar' button,
Then Multei app should update the coordinates on database using the uuid
And mark the parking report as completed (field timestamp completed_at)

 3. Handle error on complete the parking report
Given the user has already clicked on the 'Finalizar Button',
When some error happens,
Then they should find a message 'Algo não deu certo! Por favor, tente novamente.'
And they should be able to update location and click on the 'Finalizar' again

Checklist do kickoff
 A análise da história está concluída?
 QA (ou pessoa que assumiu o papel de QA) revisou a análise?
 A história está completa com todos os detalhes e as informações relevantes?
(Ex.: Contexto, Escopo, Fora de Escopo, Critérios de aceite, etc);
 O valor de negócio da história está bem entendido? (se aplicável)
 Esta história não tem dependência de outras histórias futuras?
 Não existem dívidas técnicas (débitos técnicos) relacionadas a história;
 Há protótipos de telas para essa história (se aplicável)
 Há detalhes na história de mensagens de erro e outros feedbacks para o usuário (se aplicável)
 Há mensagens de ajuda ou outros textos definidos na história (se aplicável)
 A história está em um tamanho adequado
 Existe feature toggle para a feature (se aplicável)
Checklist do deskcheck
 Há testes unitários que validem a implementação? (se aplicável)
 As alterações de código passaram em todas as pipelines
 A história foi executada manualmente
 A história não trouxe regressões ou impacto negativo a outras implementações
 Todos os critérios de aceite foram cobertos
 A história não precisa de feedback ou correção
 Foi testada uma jornada completa do usuário através da história (se aplicável)
@jimmyandrade jimmyandrade added invalid user story labels on May 4, 2020
@jimmyandrade jimmyandrade added this to the Report parking MVP milestone on May 4, 2020
@jimmyandrade jimmyandrade changed the title [User Story] Ask for location permission [User Story] Ask and handle location permission on May 4, 2020
@jimmyandrade jimmyandrade mentioned this issue on May 4, 2020
[Epic] Parking report complete journey #185
Open
@thomazmz thomazmz assigned thomazmz, heitorbffi and lemenezes and unassigned thomazmz on May 19, 2020
@jimmyandrade jimmyandrade mentioned this issue on May 20, 2020
[User Story] Show map using location data #183
Open
21 tasks
@heitorbffi heitorbffi unassigned lemenezes and heitorbffi on May 20, 2020
@heitorbffi heitorbffi removed the invalid label on May 20, 2020
@tuliooassis tuliooassis self-assigned this on Jun 29, 2020
@tuliooassis tuliooassis assigned lemenezes on Jul 3, 2020
@lemenezes lemenezes unassigned lemenezes and tuliooassis on Jul 6, 2020
@lemenezes lemenezes closed this as completed on Jul 6, 2020

Contexto de uso: Inconclusivo
Categoria: Inconclusivo