Major JQL bugfixes
This commit is contained in:
@@ -210,6 +210,21 @@ summary. Company is resolved from the SKU prefix (`SH`/`OK`) via
|
||||
usually blank, the app falls back to the joined deliverable
|
||||
descriptions for the Summary column when there's nothing else there.
|
||||
|
||||
## Resetting the local database
|
||||
|
||||
**Reset Local Database** in the toolbar clears every cached order (with
|
||||
a confirmation first). This is always safe - JIRA is the real source of
|
||||
truth, this is just a rebuildable cache - but it's worth knowing when
|
||||
you'd actually need it: if a ticket transitioned status under an older,
|
||||
buggy version of this app, its `fulfilled_at`/`cancelled_at` timestamp
|
||||
can get stuck wrong, since those are only recalculated **at the moment
|
||||
of a transition** - re-importing an already-transitioned ticket finds
|
||||
"no status change" and never touches that timestamp again. A reset
|
||||
clears the stale value entirely; the next Import from JIRA then stamps
|
||||
everything correctly from scratch. Follow a reset with **Import from
|
||||
JIRA**, and **Pull Tracking Numbers** if you rely on today's
|
||||
already-pulled tracking data.
|
||||
|
||||
## Moving storage to your MariaDB LXC later
|
||||
|
||||
In Settings (or directly in `.env`), change:
|
||||
|
||||
Reference in New Issue
Block a user