Switch from Jira Service Management
If every support hour you deliver should end up on an invoice, a help desk that knows nothing about your clients’ contracts is the wrong shape. Move the project — issues, comments, attachments — into CherryWorks Pro and keep the email address.
Priced per agent
Every plan here has unlimited users. Anyone on the team can pick up a case — the person who did the project work usually should.
Support lives apart from billing
A case belongs to a client, a project and a rate. Hours logged on it are approved, invoiced and paid out with everything else.
Another portal, another set of credentials
Your clients already have a portal for invoices and payments. Cases are in the same one, opened with a one-time link.
Reports about tickets, not about the firm
Support shows up where you run the business: utilization, project profitability, payouts, AR.
Built for IT departments
No queues, request types or automation rules to configure before a client can email you. Point the mailbox at it and the first case exists.
Jira Service Management capabilities as documented by Atlassian for its cloud plans; check your plan for specifics.
Connect: Support → Settings → enter your Jira site, project key, email and API token. The token is stored encrypted.
Import: issues become cases (status, priority, reporter, comments, attachments), each keeping a reference to its Jira key.
Switch the mailbox: point your support address at the connected Microsoft 365 mailbox. New emails become cases from that moment.
Invite clients: each contact gets a portal link by email. No accounts to create on their side.