Three applications that know about each other
Each works on its own and is licensed on its own. Together they share sign-in, the user directory and their links: a wiki page shows the state of the issues, an issue points at the documentation, and a customer request in the service desk becomes an issue without anybody retyping it.
MGProject
3.0.2
Issues, sprints and hours in one system
A complete issue tracker for teams who would rather not spread projects, support and development across three tools. You define the issue types, workflows, fields and screens yourself — and nobody else decides when any of that changes.
- Issues and workflowsYour own issue types, transitions, conditions and post-functions. Fields, field configurations and screens per project.
- Scrum and KanbanBacklog, sprints with a goal and a length, a board with swimlanes, burndown, and a planning overview across every project.
- Service desk connectionTickets from MGService or Jira Service Management become issues and keep where they came from — even when an issue is split at the end of a sprint.
- Time trackingHours booked on the issue, clock-in and clock-out with a daily journal, and reports by person, project and period.
- Search and reportingThe MQL query language, saved filters, dashboards with gadgets, and reports with PDF and CSV export.
- ConnectionsSign-in through Entra ID and passkeys, Bitbucket projects and repositories on epics, and an importer for existing Jira projects with their issues, sprints and worklogs.
MGWiki
3.0.2
What the team knows, in one place
A wiki with spaces, page trees and versions. Meant for documentation that grows alongside the daily work, and that therefore has to be quick to write.
- WritingAn editor with tables, images, code blocks and templates. Every change makes a version; versions can be compared and restored.
- StructureSpaces, nested page trees, labels and a full-text search that reaches into attachments as well.
- MacrosTables of contents, page lists, notice boxes, status markers, diagrams and embeds from MGProject.
- Working togetherComments, mentions with notifications, watch lists and drafts nobody else can see.
- Public help pagesPublish selected spaces as a lean, readable help site — no sign-in for your customers.
- PermissionsRights per space and per page, sign-in through Entra ID or locally, and read-only mode for expired licences.
MGService
3.0.5
A service desk with portal, queues and SLA clocks
A service desk in its own right, for teams who take in requests from customers rather than manage their own work. Customer portal, queues, SLA clocks and a mailbox that turns into tickets. Grown out of MGProject and near enough identical to look at — the difference is what it is for.
- Customer portalA lean surface for your customers: raise a request, follow it, reply. With live chat when it needs to be quick.
- QueuesOpen, assigned, untouched — put together per project, with the count in the sidebar and editing right in the row.
- SLA clocksFirst response, resolution and time waiting on the customer, each against the target that fits best. Paused while the customer is the one to act.
- Mailbox intakeA Microsoft 365 mailbox is fetched; every mail becomes a ticket and every reply a comment on it — exactly once, even when two fetches overlap.
- Customers and organisationsRequests can be shared with colleagues; organisations decide who gets to see what.
