multei / multei/web

[User Story] Show map using location data

Open
#183 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

user story
Dominant language
JavaScript
Stars
3
Forks
2
PR merge metrics
No merged PRs in 30d

Description

User story

As a user who is creating a parking report
I want to view a map with the location of the car
So that I can confirm that I am informing the correct 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. After obtaining user authorization to get their location (#181), we need to show the result to the user as a map.

Describe alternatives you've considered
It would be also possible for the user to type their address, instead of using GPS.

In scope

  • Give user the chance to try to obtain the address again, by clicking on "Atualizar localização".

Out of scope

Show map with address to the user on the same screen.
Ask for user permission to use GPS (#181 ).
Offering a field for the user to type their address, in case the GPS was incorrect, not available, or the user did not authorize using GPS (#208).

Acceptance Criteria

  • 1. Happy path (user sees the correct location on map)
    Given the user has chosen an image to proceed with the parking report
    When the user clicks to accept informing their position by GPS
    Then the page shows "obtendo localização"
    Then the page shows the map with the user location marked.
  • 2. Alternative path (give user the chance to try to click and see address again)
    Given the user has seen the map with the address marked
    When the address marked is wrong
    Then the user can click on "atualizar localização" to try 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)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the parking-report flow and the GPS authorization work referenced in issue #181. Confirm whether the checked acceptance criteria are already implemented; completion means showing the user's location on a map and allowing “Atualizar localização” to retry, with the unit-test coverage noted in the deskcheck.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend, web-dev
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.