Skip to main content

​
Getting Started

Connect your Atlassian site to give Blocks access to Jira issues and Confluence pages. Once connected, Blocks can look up tickets, reference documentation, and pull sprint or project context when working in GitHub, Slack, and other platforms.
Blocks cannot be invoked from Jira or Confluence. Atlassian is used as a data source only — Blocks reads from your Atlassian site to provide context when handling requests made elsewhere.

​
Setting Up the Atlassian Integration

Connect Atlassian via Settings > Integrations > Atlassian in the Blocks dashboard. OAuth connects your Atlassian site at the workspace level. Each team member can optionally link their individual Atlassian account for personalized access.

​
What Blocks Can Do

Once your Atlassian site is connected, Blocks can:
  • Look Up Jira Issues: Retrieve issue status, details, assignees, and linked tickets for relevant context
  • Reference Confluence Documentation: Find and read architecture docs, decision records, onboarding guides, and other Confluence content
  • Pull Sprint and Project Context: Understand what your team is working on when implementing features or answering questions
  • Provide Richer Context: Use Atlassian content to give more accurate answers when you make requests in GitHub or Slack

​
Using Atlassian in Requests

After connecting your Atlassian site, you can ask Blocks to reference your Jira or Confluence content from any supported platform: 
@blocks implement the feature described in PROJ-123

@blocks check the Confluence architecture doc and explain how this service fits in

@blocks what issues are blocking PROJ-456?

@blocks summarize what's in the current sprint and help me prioritize
Blocks will automatically look up relevant Jira issues and Confluence pages when it would help complete a request. You can also explicitly reference a ticket ID or page name in your request.

​
Best Practices

  • Reference Ticket IDs: Including a Jira ticket ID (e.g. PROJ-123) in your request helps Blocks find the right issue quickly
  • Name Confluence Pages: Mentioning the name of a specific Confluence page or space helps Blocks locate the right documentation
  • Keep Tickets Updated: Blocks reads current Jira status and details — stale tickets may result in outdated context
  • Combine With Other Integrations: Atlassian works best alongside GitHub or Slack, where Blocks can act on the context it finds

​
Next Steps

New to Blocks? Check out the Getting Started guide to learn the basics. Learn more about: