Connect Jira

Each comment becomes an issue in the Jira project you choose, with its screenshots attached. Replies become issue comments, the assignee follows Drobber, and the status goes both ways: move the issue to Done and the comment is resolved. Jira Cloud only (sites on atlassian.net). Comes with every paid plan and the free trial, but not AppSumo Tier 1. On Tier 1 it shows blurred under a box saying it comes with Tier 2; see AppSumo codes.

Connect Jira#

1. Open the menu under your name and choose Integrations.
2. On the Jira card, press Connect Jira and approve Drobber in Atlassian. Drobber uses the first Jira site your Atlassian account can open.
3. Back in Drobber, you see "Jira is connected. Now choose where each project’s comments should go."

To use a token instead (or where one-click isn’t offered), open Use a token instead and fill in:

• Jira site: the address you open Jira on, such as https://yourcompany.atlassian.net.
• Atlassian email: the email you sign in to Atlassian with.
• API token: create one under your Atlassian account’s Security settings, in API tokens.

Only the workspace owner can connect Jira for every project.

Choose where each project’s comments go#

Connecting Jira doesn't send anything yet. Each project is turned on separately, and each can go to a different Jira project.

1. On the Integrations page, open Projects under Jira. It shows how many projects are on, such as "0 of 4 on".
2. Next to a project, choose a Jira project from the list and press Turn on.

Or do it from the project: open its Settings tab, find Connected tools, press + Connect a tool, open Jira, choose an answer to "Which project should new comments go to?" and press Turn on. Any team member who can open the project can do this, not only the owner.

The list only offers what Jira itself returns for the connected account, so if what you want is missing, check that account can see it. "Nothing found to send to" means Jira returned nothing: create one there first, then reload. To move a project later, use Change on the Integrations page, or Send somewhere else in the project's Connected tools.

Projects are listed as name, key and issue type, such as "Website (WEB), Task". Drobber makes Task issues if the project has that type, otherwise its first type that isn’t a subtask.

What the issue contains#

The summary is the comment’s number and the start of its text. The description has the comment, who left it and where, the browser and device, links to the page and to Drobber, and developer details when Testing tools are on. Up to three screenshots are attached. See How integrations work.

• Replies: added as comments on the issue.
• Status: Drobber moves the issue through your workflow to a status that matches, using the transitions the workflow allows from where it is.
• Assignee: set to the Jira user with the same email as the person assigned in Drobber. If there’s no such user, the assignee is left as it is.

What comes back#

Status changes made in Jira come back: a status in Jira’s Done category resolves the comment, one named for review or feedback moves it to Feedback, and anything else to In Progress. A one-click connection hears about changes instantly; a token connection checks every three minutes. Comments and assignee changes made in Jira don’t come back.

Use a different account for one project#

In the project's Settings, under Connected tools, open Jira and choose Use a different Jira account for this project. Enter that account's details, press Connect Jira, then choose where comments go and press Save. The project then shows Connected rather than On, using the workspace connection.

Turn it off or disconnect#

• One project: press Turn off next to it on the Integrations page, or in its Connected tools (Disconnect, if it uses its own connection).
• Every project: the workspace owner presses Disconnect on the Jira card, then Disconnect Jira. Every project using the workspace connection stops sending. Projects with their own connection carry on.

Nothing is deleted in Jira: each issue stays where it is. Drobber does forget which issue belongs to which comment, and removes any webhook it set up there. If you turn it on again later, a new reply on an older comment starts a new issue, and status changes on older comments are not sent.