Request a seat
Connections
Docs menu

Connections

Jira and Zendesk notes from a deal

Let reps add a deal's details to a Jira issue or a Zendesk ticket, and file a Jira issue from a call. Turning it on, what gets sent, and what each result means.

When your workspace has Jira or Zendesk connected, Goose shows the company's open tickets on a deal. An admin can also let Goose write back:

  • Jira: reps comment on an issue with the deal's details, and file a new issue from a call.
  • Zendesk: reps add the deal's details to a ticket as an internal note.

Goose never sends anything on its own. The rep sees the exact text first, and it goes only when they confirm.

Turn it on (admins)

Open the account menu at the bottom of the left rail, choose Settings, then Integrations. Under Jira or Zendesk, find Let Goose create Jira issues and comments or Let Goose add internal notes to Zendesk tickets.

  1. Press Allow Goose to write. Goose explains what Jira or Zendesk will ask for.
  2. Press Continue to Atlassian or Continue to Zendesk, and sign in as a Jira or Zendesk admin. Allow the extra access it asks for.
  3. Back in Goose, the row reads Off · write access granted. Press Turn on.

Writing is on as soon as you press Turn on. If you're not an admin, the row says an admin can turn it on.

To stop, press Turn off. Goose stops sending at once. Everything it already sent stays in Jira or Zendesk. Goose then offers to take back the write access in Atlassian or Zendesk too. Press Continue to Atlassian or Continue to Zendesk to do that, or Skip to keep the access and leave writing off.

If Zendesk posts a Goose note as public, or refuses one, Goose turns Zendesk writing off, and the row says why and on which ticket until an admin presses Turn on again.

Who it shows as

Jira and Zendesk show the admin who connected them as the author of every comment and note. That's why the text always ends with the rep's name: From Goose, posted by the rep (and Filed from Goose by the rep on a new Jira issue).

Comment with deal context

  1. Open the deal, then press the company's name under the deal's title. The company card opens.
  2. Under Open tickets, find the ticket or issue. Press its ⋯ menu, then Comment with deal context.
  3. Add Your note (optional): why it matters to this deal, for example a fix they need before they sign.
  4. Read the text under Exactly what Goose sends to Jira (or Exactly what Goose adds to the ticket). It's your note, then a Deal context block, then your name. The block lists the account, the deal, its amount, stage, close date, and whether it's a renewal or new business. Nothing from calls or emails goes in.
  5. Press Post comment for Jira, or Add internal note for Zendesk.

A Zendesk note is always internal: the customer can't see it. On a Jira Service Management request, the comment is internal too, so the customer isn't emailed.

If the deal changes while you're reading, Goose says so and shows the new text. Read it again, then send.

File a Jira issue from a call

On a past call, either in the deal's list of calls or in the call's own header, press File in Jira.

  1. Goose drafts a title, a description and an issue type from the call.
  2. Change any of it: the Jira project, the Issue type, the title and the description. Then press Review.
  3. Goose checks Jira and this company's tickets for an issue that may already cover it. If one does, press Link this instead to link it to the deal. Nothing is sent to Jira.
  4. Read the exact text, then press File in Jira.

File in Jira isn't offered on a private or hidden call.

What happens after you send

Each comment, note and filed issue is saved in the deal's history, under Jira history or Zendesk history in the company card.

You seeWhat it means
SendingGoose is sending it now.
A sent rowIt's in Jira or Zendesk. Press Open in Jira or Open in Zendesk to see it there. To change it, edit it there.
FailedNothing reached Jira or Zendesk. The row says why. Retry sends the same text.
Not confirmedIt may already be there. Check the issue or ticket before you retry, or it may be added twice. Goose asks before it retries.

Only the person who sent it, or a team lead, can retry it.

When it's off

  • Another customer's ticket. A ticket linked to a deal can belong to a different customer, for example a bug two customers share. In the history it shows as a Shared bug with the other customer's name. Comments and notes stay off on it, so one customer's deal details never reach another customer's ticket.
  • Writing is turned off. The rep sees that an admin can turn it on in Settings › Integrations.
  • The connection has lapsed. An admin reconnects it in Settings › Integrations. See Reconnect or disconnect.
  • A read-only seat can't send. Your plan or seat has to allow editing.
  • Zendesk made a note public. If that happens, Goose turns off notes to Zendesk for the whole workspace until an admin turns them back on.