Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement Bug Archive Feature in Admin Dashboard - User Story 2 #53

Open
wants to merge 56 commits into
base: f24
Choose a base branch
from

Conversation

galishaq
Copy link

@galishaq galishaq commented Oct 20, 2024

This pull request introduces the Bug Archive feature in the Admin Dashboard for User Story 2. The primary goal is to allow admins view all submitted bugs/feedbacks through the dashboard. While the core functionalities are implemented, there are issues preventing the full user story from being completed due to a POST request being forbidden.

New Files Added:

  • src/views/admin/dashboard/bug-archive.tpl: Template for rendering the Bug Archive page in the Admin Dashboard.
  • public/src/admin/dashboard/bug-archive.js: JavaScript file handling the logic for fetching and displaying bug reports.
  • public/openapi/read/admin/bug-archive.yaml: API documentation for bug archive endpoints.

Modified Files:

  • src/controllers/admin/dashboard.js: Updated to include methods that handle bug report fetching and management.
  • src/admin/routes.js: New routes added for handling Bug Archive requests.
  • node_modules/nodebb-theme-harmony/templates/partials/sidebar-left.tpl: Modified to include the logic for linking the bug/feedback form to the bug archive functionality.
  • src/views/admin/partials/navigation.tpl: Modified to include the Bug Archive page button in the sidebar of the admin dashboard

Current Issues for not completing the User Story :
While the feature components have been fully built and the correct routes are in place (which can be seen in the partial testing pull request), the form is not sending data to the archive due to an issue with the form submission process. POST requests for submitting bug reports are being blocked due to forbidden errors only when the data is being sent from the form submit button (Yet when I post it manually its working through the chrome index tool ). As a result, the form and bug archive are not fully connected, preventing the form data from being successfully submitted to the Bug Archive

resolves #17
resolves #43
resolves #44
resolves #45

Ghalya AL-Eshaq and others added 30 commits September 27, 2024 01:40
…he bug archive bug to handle bug retrval and rendering in the bug archive page
…submitted bugs/feedback in the admin dashbored
…ly link it with the js file of the bug-archive
…he bug data to the server and stores it in the database
… when the page is loaded or when the submit button is clicked
… its seding the content to the the bug archive page in the admin dashboared
…rm to the admin page in sidebar-left.tpl & admin.js
…bmitBug and getBugArchive to handle the retival and rendering of the bugs correctly
…mit the bug/feedback without being an admin
…ashboared to define the route GET /api/admin/dashboard/bug-archive in schema docs
@galishaq
Copy link
Author

galishaq commented Oct 20, 2024

Fixed the csrf token error and POST forbidden but now. I'm facing a new issue where the data is being sent to the bug archive page yet it's not being regcognized as data but rather as $

…nch which contains the submitting bugs feature logic

Add Automated Tests for Bug/Feedback Form and Bug Archive Page - User Story 2
@Hakaabi Hakaabi self-requested a review October 20, 2024 18:29
Copy link

@Hakaabi Hakaabi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Impressive! looks good to me

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment