Helping you handle TDX tickets more efficiently.
Ticket Assister (stylized TkAst) optimizes your workflow with TeamDynamix (TDX) tickets by setting defaults, filling out forms, and consolidating information. It reduces your cognitive load so that you can focus on getting work done accurately and efficiently.
It has many features, all of which can be toggled on and off in the Options page.
Install deps
npm
npm install
project dependenciesMake sure that package.json
and manifest.json
have their version numbers bumped
npm run build
This will build for production, i.e. for URLs at https://help.uillinois.edu/TDNext/*
npm run build:dev
This will generate files in the build/
directory
build
directory will be removedTwo main scripts are ran in this command:
vite build
node buildContentScripts.mjs
Zip the output files
Zip all of the files from the build/
directory.
Do not zip the build
directory in itself. Only the contents.
Name the zipped file
YYYYMMDD_tkast_X.Y.Z.zip
YYYYMMDD
is the current date (which the files were built)X.Y.Z
is the version numberSave the zip file in the releases/
directory
Upload package to the relevant extension store
This repository partially automates the build pipeline for the Chrome Web store.
Update the version in manifest.json
and package.json
and merge these changes into main
git tag
the latest commit with the version number (e.g., 1.0.0
)
A GitHub action will trigger to create a release and associated artifact. Download the artifact zip file
Upload the artifact zip file to the Chrome Web Store via the developer dashboard
As of September of 2023, this repository is configured to continue to deploy under the original "Alpo" developer account. This may change in the future.
Tests are ran automatically with each commit to a pull request.
Manually run unit tests with npm run test
Manually run integration tests with npm run test-integration
To install locally and manually test the extension, see CONTRIBUTING.md
Issues and PRs are welcome. See CONTRIBUTING.md to get started.
This product is supported by Elijah Mock, Cybersecurity, and Technology Services on a best-effort basis.
As of the last update to this README, the expected End-of-Life and End-of-Support dates of this product are February 2024.
End-of-Life was decided upon based on these dependencies:
Chrome Manifest V3 (undocumented; expected January 2025 or later based on V2 retirement timeline)
TeamDynamix (quarterly; possible breaking changes February 2024)
Cerebro (unknown; dynamic release schedule)