Bug #11947
openSupport #11764: E-commerce pending tasks for nov 15 release
Support #11923: Prepare the Faq implementation work flow document with real time wireframes , merging support-desk & enquiries
Issues in FAQ workflow
100%
Description
1. When I try to add the second FAQ, I get the following error: "There is already data with templateKey: 'null'. Please use another one!"
2. Since the Store FAQs and FAQ Categories are the almost same, we can combine both into a single section instead of maintaining them separately, right?, We can add a dropdown arrow on the Category List page to expand each category and display its associated FAQs directly there.
3. When creating a category, an icon is selected. The same icon should also be displayed in the Category column on the Category List page.
4. Even after turning off the Live option, it does not get disabled immediately. Similarly draft also.
5. There are 3 FAQs in the Store FAQs section under one category. I changed the status of one FAQ to Draft, but the FAQ Categories section still displays all 3 FAQs instead of only the 2 published FAQs.
6. In the E-commerce FAQ section, clicking the Yes or No buttons under "Was this helpful?" is taking too long to respond.
7. When opening the FAQ page in E-commerce, only 4–5 categories are displayed initially, and the remaining categories appear one by one after a delay. Instead, all FAQ categories should load and be displayed at once without gradual loading.
8. When logged in with a Customer Service Representative account, the error message "You do not have permission to perform this action" appears whenever I try to open any page or perform any action. This seems to be a role-based permission issue.
9. In the Admin FAQ list, add an "Assigned To" column to display the person or team to whom each FAQ has been assigned. This will help Admin easily identify who is responsible for each FAQ.
10. Once an FAQ is assigned to a specific person, the assignment should be saved and remain associated with that person. Currently, when I click again to view the assignment, it defaults to the first person instead of displaying the previously assigned person.
11. Fetch real staff users for the "Assign to" dropdown. When an Admin assigns an FAQ to a specific user, that FAQ should be visible in the assigned user's account. Only the assigned user should be able to see the FAQ assigned to them.
12. In faq-enquiries, Reply by email is not working.
Subtasks
Related issues
Updated by Ajit A 3 days ago
- Estimated time set to 8:00 h
Repository: evergreen_pos_be
Bug or feature: Prevent duplicate key error on FAQ templateKey unique sparse index Fix: Removed default: null from templateKey in
Faq-model.js
and conditionally omitted empty templateKey values during FAQ creation in
faq.service.js
with automatic legacy cleanup to prevent sparse index collision.
Repository: evergreen_pos_fe
Bug or feature: Consolidate Store FAQs and FAQ Categories into an expandable category accordion view Fix: Unified FAQ categories and item management on
FaqsPage.tsx
with expandable category accordions, inline FAQ creation, category modal management, and redirect rules in
router.link.tsx
.
Bug or feature: Selected category icon was missing from the Category column on Category List Fix: Updated
FaqCategoriesPage.tsx
and
FaqsPage.tsx
to render the chosen category icon with graceful emoji and letter-avatar fallbacks.
Bug or feature: Delay when toggling Live/Draft FAQ status and Category Active status Fix: Implemented optimistic UI updates in handleTogglePublish and handleToggleCategoryActive across
FaqsPage.tsx
and
FaqCategoriesPage.tsx
with automatic error rollback.
Bug or feature: Category FAQ count displayed total items instead of published FAQ count Fix: Updated Category table and header badges in
FaqCategoriesPage.tsx
and
FaqsPage.tsx
to clearly show {publishedCount} Live along with total counts.
Bug or feature: Admin menu item hidden in sidebar when user in Admin role has Service Manager in assigned roles Fix: Refined role validation in
Sidebar/index.tsx
to evaluate the user's currently active role rather than assigned roles array, preventing Admin menu disappearance for multi-role admins.
Repository: evergreenpos_E-commerce_new
Bug or feature: Slow response when clicking Yes/No on "Was this helpful?" in Storefront FAQs Fix: Converted helpful voting in
FaqHelpfulVote.tsx
to an optimistic, non-blocking flow that updates local state and storage instantly while submitting API feedback in the background.
Updated by Ajit A 3 days ago
- Status changed from In Progress to Resolved
- % Done changed from 80 to 100
Bug or feature: Customer Service Representative 403 Forbidden permission error on FAQ & tickets Fix: Added alias resolution in nursery.token.js, rbac.service.js, assignment.service.js, and defaultRoles.json mapping customer_service_representative to service_manager, granting correct module access and permissions across ticket handling and ecommerce management.
Bug or feature: E-Commerce storefront FAQ categories gradual/delayed loading Fix: Updated FaqPage.tsx to initiate an immediate fetch on initial mount and restricted the debounce timer exclusively to search input changes, preventing staged loading of categories.
Bug or feature: Missing assigned user tracking and persistence in Admin FAQ management Fix: Added assignedTo field to Faq-model.js referencing NurseryUser, updated faq.service.js to populate and persist staff assignments, and updated FaqFormModal.tsx to fetch real staff users dynamically from /nus-user/getAll while correctly preserving assigned state across edit operations.
Bug or feature: FAQ account-level isolation for staff users Fix: Updated getFaqs in faq.service.js to inspect the requesting user role; admins retain full FAQ visibility across the organization, whereas non-admin staff users are strictly scoped to FAQs assigned to their user ID.
Bug or feature: Missing "Assigned To" visual indicator on Admin FAQ list Fix: Added an "Assigned To" status badge to each FAQ row in FaqsPage.tsx, displaying the assigned staff member's name and role.
Bug or feature: "Reply by email" button in FAQ enquiries failing or unresponsive Fix: Replaced direct window.location.href = mailto: navigation in FaqEnquiriesPage.tsx with a non-blocking invocation and enhanced the reply modal with direct "Open in Gmail Web", "Default Mail App", and "Copy Email" options.