Jira

The Jira integration brings your Jira Cloud projects into the conversation. Once an admin connects your Jira site:

• Channels subscribe to projects and get a card for each new issue, with a reply under it when the issue moves or is assigned, and, if you pick them, its comments.
• The same card stays current. When the issue’s status, assignee or summary changes, its card changes in place instead of adding another message.
• Move and Comment buttons on the cards act in Jira.
• Links show a preview. Paste a link to an issue on your site, and everyone in the conversation sees its status, type and assignee.
• /jira subscribes a channel from the chat, and Create Jira issue in any message’s ⋯ menu turns the message into an issue.

Jira posts as its own member, Jira, so its cards are easy to tell apart from people. It works with Jira Cloud sites (your-company.atlassian.net). Jira Data Center and Server aren’t supported.

Connect Jira

Only owners and admins can connect it. Freesbe acts in Jira as the person who connects it, so connect with an Atlassian account that can browse the projects your channels will follow, and create issues and comments in them.

1. Open Workspace settings → Integrations & apps → Integrations → Dev tools and click Connect Jira.
2. Atlassian asks you to allow Freesbe. If your account is on more than one site, pick the one to connect, then click Accept.
3. Atlassian brings you back to Freesbe, which says Jira connected.

A workspace connects one Jira site. Changes made from Freesbe show in Jira under the connecting person’s name, and the comment says who in Freesbe made them. To stop, click Disconnect: Freesbe removes its webhook from your site, and cards, previews, /jira and Create Jira issue stop. To remove Freesbe’s access in Atlassian too, open your Atlassian account’s Connected apps. If the access is removed there first, Freesbe shows Needs reconnecting until someone connects again.

Subscribe a channel

A subscription says which project posts into which channel, and what about. Add one in either place:

• In settings: under Channel subscriptions, click Subscribe a channel, pick the project and the channel, and tick what to post.
• In the channel: type /jira subscribe OPS, with the project’s key. Anyone in the channel can do it, for a project the connecting person can browse.

A new subscription posts new issues, status changes and assignments. You can also pick comments:

Pick	Posts
New issues	A card when an issue is created
Status changes	A reply under the issue’s card when it moves, like To Do → Done
Assignments	A reply under the card when someone is assigned
Comments	A reply under the card for each comment

To keep a busy project quiet, list labels under Only these labels, like customer, urgent: only issues with one of them post. In the channel, add label:customer to the command.

An issue that moves before it has a card in the channel gets one then. Open a subscription’s ⋯ menu to Post a sample card, Edit it, turn it off for a while, or delete it.

The cards

An issue’s card shows its key and summary, its status, type, priority, assignee and reporter, and its labels. The dot by the status says where it is: ⚪ to do, 🔵 in progress, ✅ done.

When the same delivery comes from Jira twice, it’s posted once. Cards stay current for 90 days; after that, a new event about an old issue posts a new card.

Act from the card

• Move asks where to move the issue, from the moves its workflow allows (Start, Done and so on). The issue moves in Jira with a comment saying who moved it (Moved from Freesbe by Maya Chen), and the card changes right away.
• Comment asks for a comment and adds it in Jira, signed with your name.
• Open in Jira opens it in your browser.

Anyone in the channel can use them, without a Jira account of their own.

Create an issue from a message

In any message’s ⋯ menu, click Create Jira issue (or type /jira create). Pick the project and the issue type, and Freesbe fills in the summary and description from the message for you to change. The projects the channel is subscribed to come first.

The issue’s description links back to the message, and its card is posted in the message’s thread, so the conversation and the issue point at each other. Projects with required fields beyond these, like a component, say so in the dialog; create those issues in Jira.

Link previews

When someone posts a link to an issue on your connected site (https://your-company.atlassian.net/browse/OPS-7), Freesbe adds a preview under the message with its summary, status, type, assignee and labels. A message gets up to three previews. Links to other Jira sites get none.

Previews come from the connecting person’s access, so people see issues they might not be able to open in Jira. Turn off Show a preview under Jira links if you’d rather they didn’t.

/jira

Command	Does
/jira subscribe KEY [features]	Subscribes the channel, optionally to the features listed
/jira unsubscribe KEY [features]	Stops some or all of what it posts
/jira list	Lists what this channel follows
/jira create	Opens a new issue
/jira help	Shows these

The features are created, status, assigned and comments.

Privacy

Freesbe keeps your site’s address, which projects each channel follows, and the access Atlassian gives it, encrypted. It reads issues only to show cards and previews. Jira sends Freesbe changes through one webhook on your site, for the projects your channels follow, to an address that doesn’t name your workspace.

Troubleshooting

• Connect Jira is greyed out: Jira isn’t set up on this server yet.
• Nothing posts: check the connecting person can browse the project, and that the subscription is on. Post a sample card checks the channel side.
• A link gets no preview: it’s on another Jira site, or previews are off.
• Move doesn’t offer the status you want: the issue’s workflow doesn’t allow that move from where it is; move it in steps, or in Jira.
• Wrong site: click Disconnect and connect again, picking the other site on Atlassian’s page.