Submitting a Request or Report
Found a bug? Have an idea? Need a doc fixed? You don't need email or a meeting — the app has a built-in form that files your request straight into the team's tracker. This page shows what to write and picks the right Type for you with a worked example of each.
Click Request / Report in the top-right header of the app, next to your name. (If you don't see it, the request service is temporarily off — try again later or let Kent know.)
The form at a glance
| Field | Required? | What to put |
|---|---|---|
| Type | yes | Bug, Feature Request, Chore, or Documentation Update (see below) |
| Priority | yes | High / Medium / Low — your honest urgency |
| Title | yes | One line that says the gist — this is what the team sees first |
| Description | recommended | The details: what you did, what you expected, what happened |
| Screenshots | optional | Up to 4 images — attach with Add image or just paste (Ctrl/⌘+V) |
As you type a title, the form shows similar open requests underneath so you can avoid filing a duplicate — if yours is already there, no need to re-file.
After you hit Submit, the request lands in the team's tracker (the Project Overseer) with your name attached, and any screenshots are saved alongside it.
Which Type should I pick?
- Bug — something is broken or wrong: an error, a wrong number, a button that doesn't work, a column that's blank.
- Feature Request — something new you'd like the app to do that it doesn't today.
- Chore — a maintenance / housekeeping task that isn't user-facing behavior: a reference list that needs updating, a cleanup, a data refresh, a small operational tweak.
- Documentation Update — this help site or an in-app explanation is missing, unclear, or out of date.
Don't overthink it — if you're unsure between Bug and Feature, pick whichever is closer and describe what you saw; the team re-labels as needed.
Worked examples
Bug — something is broken
Type: Bug · Priority: High Title: Export crashes when no service month is selected Description: On the Invoices Needing Action tab I clicked Download Excel with the Service Month filter set to "All months". Instead of a file I got a red error banner and nothing downloaded. Expected a workbook of the current run. Screenshot: the red error banner (pasted with Ctrl/⌘+V)
Why it's a Bug: the app did the wrong thing. The steps → expected → actual shape plus a screenshot lets the team reproduce it immediately.
Feature — something new you want
Type: Feature Request · Priority: Medium Title: Filter Invoices Needing Action by "Waiting on Customer" reason Description: I park a lot of lines as Waiting on Customer (NTE / PO / WO). I'd like to filter the tab by that reason so I can follow up on just the POs in one pass. Today I have to scroll the whole list. Screenshot: optional — a shot of the current filter bar helps show where it'd go
Why it's a Feature: it asks for new behavior. Leading with the outcome you want ("follow up on just the POs") helps the team design the right thing.
Chore — housekeeping / maintenance
Type: Chore · Priority: Low Title: Remove closed account "JLL – Old Warehouse" from the Third Party Customers list Description: This account closed last quarter and bills directly now, but it still shows up in the report scope. Please drop it from the Third Party Customers reference so it stops appearing.
Why it's a Chore: it's operational upkeep, not a code bug or a new feature. Chores are a great fit for reference-list edits, data refreshes, and small cleanups.
Documentation Update — the docs are off
Type: Documentation Update · Priority: Low Title: "How a Run Works" doesn't mention the new real posting date Description: The matching-logic page still says Service Month always comes from the service period. Since the August change it can use the real CieTrade posting date for needs-billing charges — please update that section.
Why it's a Documentation Update: nothing in the app is broken; the help is stale. Use this type for anything about this site or an in-app explanation.
Attaching a screenshot
Screenshots are the single most helpful thing you can add to a Bug or Feature request. Two ways to add them:
- Add image — click the button and pick a file (PNG, JPEG, GIF, or WebP).
- Paste — take a screenshot to your clipboard, click into the form, and press Ctrl/⌘+V.
You can attach up to 4 images (8 MB each). Each shows a thumbnail you can remove before submitting, and they're saved with your request so the team sees exactly what you saw.
What happens after I submit?
Your request is logged in the team's tracker with your name, the type/priority, and any screenshots. The team reviews and triages from there — you don't need to send a separate email. If you filed something urgent (High priority) and it's time-sensitive, a quick heads-up to Kent never hurts.