View Reported Issues

[mirasoldavila13]

User Story:

AS A a user or authority I WANT TO view all reported issue. SO THAT I can monitor the issues and their statuses

Acceptance Criteria:

1. The user can see a list of all issues, with details such description, location, likes and status.
2. The issues should be filterable by status (reported, in progress, resolved).
3. The user should be able to see the data and weather data for each issue.

Tasks:

• [x] Create the UI for displaying the list of issues.
• [x] Implement filters for issue status.
• [x] Create the API route to retrieve all issues.
• [x] Display the associated data (location, date, weather) in the UI.

[mirasoldavila13]

Completed:

• Created UI for displaying reported issues:

  • Designed a layout to list all reported issues, including details such as description, location, likes, and status (e.g., reported, in progress, resolved).

• Report Option Landing Page:

  • Implemented options to allow users to either report to the community or report directly to authorities.
  • Used TailwindCSS for clean and responsive design.

• RESTful API and Axios Integration:

  • Integrated RESTful API to fetch a list of reported issues from the backend.
  • Axios is used to make calls to the backend to display issues and handle interaction.

• Weather Data Integration:

• • Each issue displays the associated weather data (temperature, wind speed, condition, etc.) at the reported location using the OpenWeather API and OpenWeather Geolocation API .

• Sequelize Migrations:

  • Created migration for Issues, including fields for description, location, and status.
  • Added functionality for PostGIS to store latitude and longitude data.
  • Created feed, comments, and issues migration tables using .cjs format.

• In Progress:

  • Filtering by status (reported, in progress, resolved):
  • Developing the filtering functionality to allow users to view issues based on their status.
  • Testing the issue listing and filtering functionality:
  • Debugging the fetching and filtering process to ensure the correct display of issues and their statuses.

• Still to be Completed:

  1. Implement filtering by issue status: Add filters for users to view issues based on whether they are reported, in progress, or resolved.
  2. Finalize API route to retrieve all issues from the backend.
  3. Testing all endpoints to ensure the correct data is fetched, including location, description, and weather data for each issue.

[mirasoldavila13]

Update on User Story: View All Reported Issues (v2.0)

Completed:

1. User Interface Development:

   • Created a dedicated page for users to view all reported issues.
   • Implemented a layout that displays essential details such as description, location, likes, and status (e.g., reported, in progress, resolved).
   • Applied TailwindCSS for a clean and responsive design.

2. Filtering Functionality:

   • Implemented filters that allow users to view issues based on their status (reported, in progress, resolved).
   • Ensured the filtering functionality works correctly, displaying the appropriate issues based on the selected status.

3. API Integration:

   • Developed a RESTful API route to retrieve all reported issues from the backend.
   • Integrated Axios for seamless data fetching and interaction with the backend.

4. Weather Data Display:

   • Each reported issue now includes associated weather data (temperature, wind speed, condition) for the reported location, utilizing the OpenWeather API.

5. Database Migrations:

   • Created necessary migrations for the Issues model, including fields for description, location, and status.
   • Integrated PostGIS for storing latitude and longitude data.
   • Completed migrations for feed, comments, and issues tables.

Additional Notes:

• As the sole developer on this project, I have been responsible for all aspects of the design, implementation, and testing.
• This includes ensuring that all functionalities are thoroughly developed and documented to maintain high standards of quality and professionalism.