-
-
Notifications
You must be signed in to change notification settings - Fork 27
Report Packs
Reporting β Packs Β· Requested by Enrique Cabrera Β· π οΈ How it works underneath: Report Packs β Developer Guide
A report pack is a multi-page document you design once β a cover, headings, charts, tables and your own commentary β and export as a PDF for whatever period you choose. The monthly service report stops being an afternoon of screenshots: pick the period, read the figures, write the summary, export.
The designer works like a word processor. There is a ribbon along the top, real pages with rulers in the middle, a list of blocks to drag in on the left and the properties of whatever you have selected on the right. What you see on the pages is exactly what goes into the PDF β the same line breaks, the same page breaks.
- Open Reporting β Packs and press New.
- Give it a name. It starts with a header showing your logo, the report's name and its dates, and a Summary heading with a paragraph to fill in.
- Drag blocks in from the left.
- Press Save (Ctrl+S) and Export PDF (Ctrl+P).
Copy makes your own copy of any pack you can open β including one somebody has shared with you to view only.
The Blocks list on the left holds everything you can put in a pack. Type in the search box to narrow it (uptime, licences, priorityβ¦), and point at a block to see a preview with your real figures before you use it.
- Drag a block onto the page. A line shows where it will land.
- Drop it on the left or right edge of another block to put them side by side. If the row is full, room is made.
- Double-click a block in the list to add it after the selected block.
Pages are a grid of 12 columns. Blocks sit side by side until a row's 12 columns are used β two half-width charts, three thirds, a two-thirds table beside a third-width chart.
| To⦠| Do this |
|---|---|
| Change a block's width | Drag the handle on its side, or use Layout β Arrange, or the Width buttons in Properties |
| Change a chart's height | Drag the handle under it, or set Height in Properties |
| Move a block | Drag it, or Alt+β / Alt+β |
| Keep a block below, not beside, the one before | Tick Start a new row |
| Start a section on a new page | Select its heading and tick Start on a new page |
| Change what a chart shows | Select it β Group by, Chart type, Most shown and so on are in Properties |
Right-click any block for cut, copy, paste, duplicate, move, width and delete.
| Area | Blocks |
|---|---|
| Tickets | Ticket summary Β· tickets over time Β· by status, priority, category, analyst, team, department or origin Β· a list of the period's tickets |
| Service Status | Service uptime with a bar for every day and the incidents under each service Β· uptime table Β· incident log (every update, with its comment) Β· incident summary Β· headline figures |
| Software | By publisher Β· most installed applications Β· licences and renewals Β· headline figures |
| Assets and Intune | By type, operating system or status Β· warranties and leases ending Β· Intune compliance, operating systems and encryption Β· headline figures |
| Layout | Heading Β· text box Β· line Β· space Β· page break |
A block can be turned into its neighbour without starting again: Tickets by status becomes by priority by changing Group by, and a doughnut becomes a bar chart by changing Chart type.
Software, asset and Intune figures show the inventory as it is now, not as it was during the period β the block says so under its title.
Double-click a text box to type on the page. The Home tab then works on what you are writing:
- Font β size, bold, italic, underline, strikethrough, text colour, highlight, clear formatting
- Paragraph β bullets, numbering, indent, alignment (left, centre, right, justified)
- Styles β Normal, Heading 1, Heading 2, Heading 3
Click anywhere off the text, or press Esc, when you have finished. Pasted text arrives without its old formatting, so a report keeps its own look.
Double-click the top or bottom of any page to edit the header or footer, or the cover page to edit the cover. They work like a text box, plus Insert β Fields:
| Field | Shows |
|---|---|
| Page number / Number of pages | Page 3 of 12 |
| Start of period / End of period | The period's dates, in your date format |
| Today's date | The day the PDF was made |
| Report title | The pack's name |
| Company | The company the pack is reporting on |
Insert β Logo puts your company logo (System β Branding) wherever the cursor is.
Switch the Cover page and a Contents page on from the Insert tab. The contents list every heading marked Show in the contents, with the page each one starts on. In Properties, with nothing selected, you can choose whether the header appears on the first page and whether a line runs under the header or above the footer.
The Data tab sets what the whole pack is about:
- Period β today, yesterday, this or last week, month, quarter or year, the last 7, 30 or 90 days, the last 12 months, or your own dates.
- Company β if you work with several companies: the one you are working in, all of them, or one in particular.
Every block uses it, and the header's dates follow it. "Last month" means your last month β the period runs from midnight to midnight in your own timezone.
Refresh fetches the figures again.
- Layout β paper size (A4, Letter, Legal, A3), portrait or landscape, and margins (Normal, Narrow, Wide, or your own in Properties).
- Design β the font (Helvetica, Times or Courier), the text size, the colours of headings, accents and table headers, the chart colours, and striped table rows.
A pack is private until you share it. On the Report Packs list, press Share and add:
| Who | Means |
|---|---|
| Analyst | One person |
| Team | Everyone in the team, now and later |
| Department | Everyone whose profile has that department, however it is spelt |
Each can view or edit.
- View β open it, change the period to look at a different month, and export it. They cannot change the design (they can Copy it to make their own).
- Edit β change it too. If two people edit at once, the second to save is told who saved first and can reload or save theirs over it β nobody's work disappears silently.
Only the owner can share or delete a pack.
π Everybody sees a pack with their own access. A block from a module somebody has not been given shows them a note instead of figures, and they only see the companies they work with. Sharing a pack never shows anybody data they could not already see.
Export PDF makes the document exactly as the pages look on screen. The text is real text β you can search it and copy from it. Long tables, incident logs and uptime lists continue onto the next page with their column headings repeated, and a heading never sits alone at the bottom of a page.
The file is named after the pack and the period, for example Monthly service report - 01.09.2026 to 30.09.2026.pdf.
β οΈ The PDF uses the standard Helvetica, Times and Courier fonts, which cover English and the other Western European languages, including Spanish accents and Γ±. Text in other scripts β Chinese, Arabic, Hindi or Cyrillic, for example β shows on screen but appears as ? in the PDF. The status bar warns you when a pack contains any.
| Keys | Does |
|---|---|
| Ctrl+S | Save |
| Ctrl+P | Export the PDF |
| Ctrl+Z / Ctrl+Y | Undo / redo |
| Ctrl+C, Ctrl+X, Ctrl+V | Copy, cut and paste the selected block β also between packs |
| Ctrl+D | Duplicate the selected block |
| Delete | Delete the selected block |
| β / β | Select the previous or next block |
| Alt+β / Alt+β | Move the selected block |
| Enter | Edit the selected text |
| Ctrl + mouse wheel | Zoom |
FreeITSM β an open-source IT Service Management platform Β· github.com/edmozley/freeitsm Β· MIT licence
- Installation
- β° Scheduled tasks (cron jobs)
- Architecture
- π§ͺ Developer tests
- AI Providers
- Internationalisation (i18n)
- Timezones & Time Handling
- π Date & Time Formats
- Theming & Dark Mode
- ποΈ Recent β getting back to what you were doing
- β¨οΈ Command palette (βK)
- π Searching inside tickets
- π Attached documents
-
MobileβFriendly
- β³ π« Mobile: Tickets
- β³ π» Mobile: Assets
- β³ π Mobile: Calendar
- β³ π Mobile: Knowledge
- β³ π¦ Mobile: Service Status
- β³ πΌ Mobile: Watchtower
- β³ π§© Mobile: Problem Management
- β³ π Mobile: Change Management
- β³ πΏ Mobile: Software
- β³ β Mobile: Tasks
- β³ π Mobile: Forms
- β³ π Mobile: Contracts
- β³ π Mobile: Domains
- β³ π Mobile: People
- β³ π Mobile: LMS
- β³ πΊοΈ Mobile: CMDB
- β³ πΊοΈ Mobile: Network Mapper
- β³ π§ Mobile: Process Mapper
- β³ βοΈ Mobile: Workflow
- β³ π₯οΈ Mobile: System
- β³ π Mobile: Reporting
- β³ π Mobile: System Wiki
- β³ π Mobile: Self-Service Portal
- β³ π§° Mobile: Techniques & Tricks
-
Security
- Layer 1 β which modules you can enter
- β³ π§© Module Access Control
- β³ π οΈ Module Access β Developer Guide
- Layer 2 β what you can administer
- β³ π Roles & Permissions
- β³ π οΈ Roles β Developer Guide
- β³ π€ Why capabilities are constants
- Layer 3 β the System module
- β³ π Admin Access Control
- Hardening
- β³ π Security review response 2026-08
- β³ π‘οΈ Security hardening 2026-08
- β³ π οΈ Security hardening 2026-08 β Developer Guide
- β³ π‘οΈ Round three β plain English
- β³ π οΈ Round three β Developer Guide
- β³ π‘οΈ CSRF protection (S4) β Developer Guide
- Single Sign-On (SSO)
- ποΈ LDAP & Active Directory
- π CardDAV contact sync
- Browser Extension
- API Reference
-
π REST API β how it works
- β³ π« REST API: Tickets
- β³ π» REST API: Assets
- β³ π΄ REST API: Problems
- β³ π REST API: Changes
- β³ π REST API: Knowledge
- β³ β REST API: Tasks
- β³ ποΈ REST API: CMDB
- β³ π REST API: Contracts
- β³ ποΈ REST API: Calendar
- β³ πΏ REST API: Software
- β³ π REST API: Domains
- β³ π¦ REST API: Service Status
- β³ βοΈ REST API: Morning Checks
- β³ π REST API: Forms
- β³ βοΈ REST API: Workflow
- β³ π·οΈ REST API: Cost centres
- β³ πΊοΈ REST API: Network Mapper
- β³ π§ Using the API docs page
- β³ π OpenAPI specification
- β³ β OpenAPI: kept correct
- β³ π οΈ Maintaining the catalogue
- Watchtower
-
Tickets
- β³ π Rota copy and paste β Developer Deep Dive
- β³ β Checklists & SOPs
- β³ βοΈ Mandatory fields
- β³ π·οΈ Ticket categories
- β³ π₯ Assigning tickets to a team, and escalation
- β³ π’ One board across every company
- β³ Mailbox Authentication
- β³ π€ Email send log
- β³ Basic IMAP mailboxes
- β³ Email rendering & images
- β³ SLA Management
- β³ WhatsApp channel
-
β³
βοΈ Telegram channel - β³ β CSAT company scope and filters β Developer Guide
- β³ π₯ Microsoft Teams channel
- β³ π¨οΈ Mattermost channel
- β³ π¬ Web chat channel
- β³ π£ Slack channel
- β³ π Linking tickets
- β³ β Record previews
- β³ π Ticket notes: internal or shared
- β³ ποΈ Canned responses
- β³ βοΈ Limiting replies to particular senders
- β³ π¨ Telling the analyst a ticket is theirs
- β³ βοΈ Email signatures
- β³ π The public web address
- β³ π’ Ticket numbering
- β³ π Raising a ticket for someone else
- β³ π Merging tickets
- β³ π Confidential tickets
- β³ π₯ Portal managers
- β³ π Who has seen a ticket
- β³ π Reading long tickets
- β³ β Splitting tickets
- β³ β Selecting several tickets
- β³ ποΈ The folder pane
- β³ π½ Just my tickets, or no closed ones
- β³ π οΈ Snoozing tickets β Developer Guide
- β³ π₯ Collision detection
- β³ β±οΈ Time tracking
- β³ π Scheduled work in your own calendar
- Problem Management
- Tasks
-
Assets
- β³ π’ Moving an asset between companies
- β³ π Shared asset locations
- β³ π§βπΌ Assigning assets to analysts
- β³ π Warranty and lease alerts
- β³ π Saved table views
- β³ π¨οΈ Recording anything, and importing it
- β³ π·οΈ QR asset labels
- β³ π Who holds what, and handover documents
- β³ π₯οΈ The inventory agent (PowerShell)
- β³ ποΈ Proxmox VE servers
- β³ βοΈ VMware Cloud Director servers
- β³ π Linking equipment to tickets
- β³ βοΈ Follow-up tasks on a ticket
- Knowledge
- Change Management
- Calendar
- Morning Checks
- Reporting
- Software
-
Forms
- β³ π¨ The form designer β Developer Guide
- β³ π Layout & the grid β Developer Guide
- β³ ποΈ Collections β grouping submissions
- β³ π Submissions as PDFs
- β³ β‘ What happens next β a form's own actions
- β³ π οΈ Sections & conditional logic β Developer Guide
- β³ π οΈ Lookup fields β Developer Guide
- β³ π‘οΈ Catalogue request approvals
- People
- Domains
- Contracts
- Service Status
- π Notifications
- π¨ War Room
- Self-Service Portal
- LMS
- Process Mapper
- CMDB
- Network Mapper
- Workflows
- Issue trackers (Jira, Azure DevOps)
- System
-
Overview
- β³ π Progress tracker
- β³ Concepts & vocabulary
- β³ Email routing & mailboxes
- β³ Settings: global vs per-company
- β³ Users & self-service
- β³ Staff cross-company access
- β³ π’ One board across every company
- β³ Worked examples
- β³ Pitfalls & gotchas
- β³ Scope: what it's for
- β³ π οΈ Developer Guide (make a module multi-company)
- β³ ποΈ Case study: CMDB (a linked graph)
- β³ π§ͺ Test harness (prove it's isolated)
- What this is
-
π Bugs resolved
- β³ π’ Chat tickets ignored your ticket numbering
- β³ π Dates shown as a dash, or in server time
- β³ π Assets β Users showed people from other companies
- β³ π Restricted analysts could read other modules' data
- β³ πΌοΈ Replies with a picture in the thread failed to send
- β³ π Reply attachments never reached the customer
- β³ π οΈ Outbound email attachments β Developer Guide
- β³ π A global SSO provider was missing from the portal
- β³ π Behind a proxy, the SSO redirect said http
- β³ βοΈ The portal tagline moved when you saved it
- β³ π¨ The portal settings screen forgot what you saved
- β³ π‘οΈ The approvals inbox said "Error" and nothing else
- β³ π A table's answers were missing from the PDF
- β³ β A single-select column let you tick every option
- β³ π The portal ignored a form's field widths
- β³ π The tasks board stopped taking clicks
- β³ ποΈ #121 The index list is out of date after upgrading
- β³ π #133 The calendar subscription was empty
- β³ π #131 Tasks always reopened on the board
- β³ π₯ #129 Every page returned HTTP 500 after upgrading
- β³ π³ #127 A PHP warning above the System page
- β³ π #126 Notes stamped with the server's clock
- β³ π Storing every date in UTC
- β³ πͺ The portal was down for everyone signed in
- β³ βοΈ #120 Workflow notes could never be written
- β³ βοΈ #123 Three errors when running Database Verification
- β³ π #122 The description box was a stub in the corner
- β³ π£ Demo data deleted real accounts
- β³ π #117 Sign-in redirected to the wrong address
- β³ π¨ #108 The priority dot was invisible
- β³ β±οΈ #116 Time logged from the right-click menu
- β³ π #114 API keys refused by our own guard
- β³ ποΈ #110 Assigning a task told nobody
- β³ πͺ #107 Signed out while still working
- β³ π #103 "Share with Requester" reached nobody
- β³ π #102 Search found nothing for hyphens
- β³ πͺ #101 Source code editor opened behind
- β³ βοΈ #88 Subtasks could not be ticked off
- β³ π» #84 Asset deep link selected nothing
- β³ π« #79 A new ticket arrived with no status
- β³ π§ #79 A ticket from email did not say so
- β³ π #78 Bell opened to nothing
- β³ π¬ #77 Mail only collected from Inbox
- β³ π #74 The default password could not be changed
- β³ π¦ #70 Renaming an impact level
- β³ π€ #67 App-only mailboxes could not send
- β³ π #45 Verify only ever worked for Microsoft
- β³ π #45 IMAP reported as not authenticated
- β³ βοΈ An email template stopped escaping itself
- β³ π The portal dashboard showed the wrong time
- β³ π’ The folder said 99 and the list showed 96