ZOVANTA SOFTWARE / KNOWLEDGEBASE

Bug reports 1.0.12 • inspected package; hosting/live validation not claimed

Bug reports — current settings and requirements

Inspected build

Bug reports 1.0.12, package key forovanta-issues. Declared core requirement: >=1.0.0-beta.149a. This is source documentation, not a fresh live-install certification. Preserve the package/data and read its update plan.

Premium: use an authorized package/license and normal core entitlement controls. A zero/absent selling price does not turn the package free.

Settings

The following labels/defaults come from the inspected manifest. The runtime may group or replace these controls with a dedicated screen; save through that screen.

Control Initial value Meaning
Bug forum (where every report is posted) "Not declared" Set this once: every bug report a member files becomes its own topic in this forum, numbered BUG-1, BUG-2 and so on, and you work them from there. Nothing is chosen per report, and nothing else has to be set up for reports to arrive here.
Bug reports account (posts the thread starter) "Not declared" The account whose name every bug report's topic is posted under. Only administrators and moderators are offered here: this is the account the tracker acts as, so it is a staff account — the member who filed the report is named in the report itself, can still reply to the thread, and is told about every answer. Choose the account you keep for the tracker — a "Bug Reports" account, say — and the thread starter in the bug forum is written as it. Leave it empty and the member who files stands as the thread's starter.
Status prefix for bug threads "Not declared" The topic prefix that marks a bug thread's current status — Confirmed, In Progress, Fixed or Cannot Reproduce.
Screenshot limit 4194304 Largest screenshot or attachment a member may upload with one bug report.
Reports per page 24 How many bug reports the public list shows on one page.
Public bug list true Whether members can browse all bug reports. When off, only the reporter and staff can read a report; when on, anyone can search and read reports, but only signed-in members can submit or reply.

Install or update

Use the addon ZIP itself in Admin → Add-ons → Upload → Review → Install/Upgrade; addon.json belongs at its root. Do not upload the complete source/recovery bundle to core Package Manager. Back up database and private files, preserve existing settings/license/enabled state, and do not uninstall as an update step. After upgrading, test the actual member and staff operations, not just the new version label.

Current operating workflow · Shared addon installation

We suggest Panelica for managing your hosting environment.