Case

cdesk

In development

An accessible command-line client for TOPdesk, following the same keyboard- and braille-first model.

What & why

The third in the family: reading and searching TOPdesk incidents from the keyboard — incident lists with FIQL filters, detail view, people and operators. Phase one (reading) is done and covered by offline tests; the interactive TUI follows once the fields are validated against a real TOPdesk environment.

The same design principles as cjira and csphere — and the same discipline: write actions are deliberately not in it yet. Validate against the real API first, only then write. Better an honest first phase that is correct than a quick demo that guesses.

Approach

The shared accessibility model as the starting point: line-oriented, identifier first, no colour-as-meaning, no popups.
The read commands first, covered by offline tests with recorded API responses.
Write methods prepared in the client layer, but not connected until live validation is in place.
A per-user application password; never credentials in the repository.

Technology

Python
TOPdesk REST API
FIQL
Offline tests first

Images & demo

$ cdesk incidents --query closed==false
I2607-201  [In progress]  Meeting room 2 display keeps going black
I2607-198  [Ready to handle]  Request access to the shared project folder
I2607-190  [Waiting for vendor]  Printer on the 3rd floor is not working
3 incident(s).

Real cdesk output over example data: incidents filtered with a FIQL query — number first, status as text.