Jira and calls
Once Jira is connected, calls can use it in four ways: the customer's requests appear on the call screen, a call can be routed by the customer's service level, every finished call can be written into Jira, and an agent can call a customer from a Jira issue.
Customer lookup on the call screen
For an incoming call, the web console and the MonoPbx phone app show the Jira Service Management customer who has the caller's number: their open requests, with priority, status and the most pressing service level (SLA).
The SLA is shown as one of these states:
| State | Meaning |
|---|---|
ok | Within the goal. |
at_risk | Less than a fifth of the goal is left. |
breached | The goal is missed. |
paused | The clock is stopped. |
The lookup never delays a call. The call screen asks once the call is shown. If Jira is slow, the screen shows a pending state and asks again. Answers are kept for two minutes, and a changed Jira webhook or a disconnect clears them. A person without jira:read, a company without a connection, an unknown caller and a failing Jira all show nothing on the call screen.
Routing by service level
A rule on the Jira settings page can send a call to a queue based on the caller's service level, for example to a senior queue when the customer's Time to resolution is breached. Before you save a rule, use the test with a number to see the decision it would make. The rule on the Jira settings page applies to the whole company.
A queue, or an inbound route that sends calls to an extension or a ring group, can have its own rule: open the queue or the route, find Jira SLA rule for calls to the number, and add a rule. Calls that arrive at that number use it instead of the company rule; every other number keeps the company rule. In a queue's own rule the queue is already filled in as the target, so a caller with an urgent request first rings the assignee (if you choose that) and otherwise waits in this queue as usual. To try a number's rule, enter its number as the destination in the test with a number.
Every decision is recorded on the call: the call history (GET /calls, the CDR) and the call.started event carry jira_route (normal, priority_queue or assignee), jira_route_reason (for example sla_breach, priority:High, or why the call kept its route, such as no_issue) and jira_issue (the issue that decided). Calls that kept their route are recorded too, so you can report how often the rule changed a route.
Creating an issue from a call
An agent can create a Jira issue from a call. MonoPbx fills the mapped fields with the caller's number, the call id and the direction, so the issue starts with the call's facts. The issue is then the one that call is logged to.
Create Jira issue (on a call, a voicemail or a customer conversation, in the web app and in MonoPhone) shows only when the company's Jira connection is working and has a project and an issue type mapped, and only to people with the jira:issues permission. The apps check this once per session, so after an administrator connects Jira, sign in again or reload the page to see the action.
Creating an issue from a customer conversation
Create Jira issue on an open inbox conversation opens an issue with the conversation's transcript. When the company has AI summaries turned on (Admin > AI, Call summaries), the issue also gets a short AI summary of the conversation: what the customer wants, what was answered and what is still open. The summary is written once, when the issue is opened, and is kept only in Jira. With AI summaries off, or if the AI does not answer in time, the issue opens with the transcript only.
Call logging
When a call ends and Jira knows the customer, MonoPbx adds a comment or a worklog to an issue. It uses the issue the call was turned into, or else the customer's newest open issue. The entry has the direction, the start time, the talk time, the agent, the customer and, when there is one, the AI summary.
Set the default mode on the Jira settings page, or per queue:
| Mode | What is written |
|---|---|
off | Nothing. This is the starting setting. |
comment | A comment on the issue. |
worklog | A worklog with the talk time. Calls shorter than a minute are written as comments. |
Each call is logged once. A repeated end report, or a late AI summary, never adds a second entry. If Jira fails, the entry is retried with growing waits, from one minute up to one hour, for up to eight attempts. After that it shows as failed, and an administrator can retry it from the settings page. Every logged, failed and retried entry and every change of the settings is written to the audit log.
Calls of customers that Jira does not know, and calls with no open issue, leave nothing in Jira.
Click-to-call from Jira
With the Forge app from integrations/jira-forge, each Jira issue shows a MonoPbx call panel with the customer's phone number and a Call button. The call goes through the agent's own MonoPbx account: the agent's phone rings first, then the customer. The dial plan and calling limits of that agent apply, as they do for any call the agent dials. The call uses the click-to-call API (POST /api/v1/calls/click-to-call).
Hide the customer's tickets from one person
A role that holds jira:read (receptionist, supervisor and up) shows the customer's requests on every call screen. If one person should keep the role but not see customer tickets, open Admin, Channels, Jira and use the card People refused Jira data: pick the person and select Refuse Jira data. Their call screens then show no Jira requests. Select Allow again to undo it. The change is recorded in the audit log, and the person is removed from the list automatically when their account is deleted. Giving someone a custom role without the Jira permission still works too.
Permissions
| To do this | You need |
|---|---|
| See the customer on the call screen | jira:read |
| Change the mapping, the rules, the call logging or retry a failed entry | jira:write |
| Refuse a person Jira data, or allow them again | jira:write |