ihompadmin/tasq
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 1 Wiki Activity
20720ba541
tasq/RELEASE_NOTES.md

3.0 KiB
Raw Blame History

TasQ Release Notes

Version: 0.0.0.1 Date: 2026-02-22

Overview

This release contains a working core of TasQ focused on task and ticket handling, user and office management, workforce features, and an initial implementation of geofencing. It is an early release intended for internal testing and iterative feature work.

Working Features

  • Tickets: Create, view, and manage tickets. Basic assignment and status updates are functional with server-side querying and provider-driven UI flows.
  • Tasks: Task creation, listing, and updates are implemented. Includes an IT job printout feature for exporting/printing IT job details and work instructions.
  • User Management: Admins can create and manage user profiles and roles. Authentication flows and profile providers are in place to support role-based access.
  • Office Management: Offices can be created and maintained; users and tasks may be scoped by office assignment for filtered views.
  • Workforce: Workforce management features such as viewing and assigning staff are implemented, including basic shift/duty assignment tooling used by the app's workforce screens.
  • Initial Geofencing: A first-pass geofencing implementation is available (admin creation of geofences and basic detection hooks). This is an initial implementation intended for iteration — see roadmap for full rollout.

Known Limitations

  • Geofencing is an initial implementation and lacks advanced triggers, notifications, and full device offline handling.
  • Duty scheduling is functional but will be improved for more complex shift patterns and repeats.
  • Reports, events, and announcements are not yet implemented.

Roadmap (Planned Features)

  • Events: Event creation, RSVP/attendance tracking, and calendar integrations.
  • Announcements & Reports: Admin announcement bulletin and a reports suite (exportable CSV/PDF) for tickets, tasks, and workforce metrics.
  • Improved Duty Schedules: Advanced scheduling, repeating patterns, and approval workflows for duty swaps and long-running schedules.
  • Geofencing (Full Rollout): Robust geofence lifecycle, realtime triggers/notifications, user/device-level geofence state, and integration with duties and timekeeping.
  • Offline Support: Local caching, queued mutations, and background sync to support intermittent connectivity for mobile users.

Tests and Quality

There are existing unit and widget tests under test/ that cover core pieces of the app (providers, time utilities, some screens). Before wide release, ensure flutter analyze and flutter test are clean.

Developer Notes

  • Follow the repository's COPILOT_README.md / CLAUDE.md guidance for theming, server-side pagination, and provider patterns.
  • Key folders: lib/providers/, lib/routing/, lib/screens/, test/.

Next Steps

  • Stabilize geofencing triggers and notification paths.
  • Implement reports and announcements with RBAC checks.
  • Add offline sync, prioritize duty schedule improvements, and add event/calendar support.