Skip to content

Following up your issues and complaints with your team in an easy way without complicated UI, and requirements. This project is planned to be built with every component developed from scratch, including custom UI components, functions, and more.

License

Notifications You must be signed in to change notification settings

sfwnisme/frontend-complaint-tickets

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Ticket Issue System

Note

This project is planned to be built with every component developed from scratch, including custom UI components, functions, and more.

Try the project

  • Website: link
  • Email: veiw_only@sfwn.me
  • Password: 123412354

Technologies Used

  • React
  • TypeScript
  • CSS Modules
  • Tanstack Query
  • Axios
  • Fully Custom, Reusable UI Components
  • React Hook Form
  • Zod
  • Visi ("bias, it's my package")

You can check the backend project here.

Project Status

Tasks

status task
done create ticket
done implement ck editor
- get tickets by department, tags, status
done ticket page
done update ticket
done modify ticket information
done add ticket to department
done ticket assign user
done remove assign user
done get all departments
done create department
done update department
done delete department
done get all tags
done create tag
done update tag
done delete tag
- search for tickets
- delete bunch of tickets
- update Inputs array component to accept select and ck editor
done show the ticket settings only for the assigned user
done show the assigned or the public tickets for the users
done prevent editing (assigned user, and department) resolved and closed tickets

How permissions works here

there is three ways to manager permissions:

  • wrapper component for the components
  • allowed roles in an array of the routes configs like sidebarPagesLinks
  • a function for custom or more complex usages

Completed Features

  • Alert message system for success and error states
  • comment component
  • create comment => implement the validation with zod
  • comments that created by the frontend with true as a solution not marked
  • skeleton loading
  • create array for inputs data with typescript interface to sure the exact required data to loop instead of adding inputs manually
  • Create Auth wrapper for the permissions, like <Permissions when={true}>...</Permissions>
  • global error handling
  • global delete dialog

Completed components

In Progress

What will be in the next version?

  • metics and charts.
  • display only the related ticket.
  • user's profile page.
  • notifications.
  • pagination

Backlog

Note

Some ideas shine through working on this project, thus it included below as a backlog tasks

  • Comprehensive text component system with:
    • Type variants (h1, h2, h3, h4, h5, h6, p, small, 12px, 11px)
    • Color variants (primary, info, danger, success, warning)
    • Font weights (200, 400, 500, 600, 700, 800, 900)
    • Standardized sizing for application consistency
    • Padding and margin props to avoid CSS modules nesting issues
  • buttons for next and prev ticket on the float ticket component header
  • global error handling

About

Following up your issues and complaints with your team in an easy way without complicated UI, and requirements. This project is planned to be built with every component developed from scratch, including custom UI components, functions, and more.

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Contributors 2

  •  
  •  

Languages