Jira Integration

Connect Pointing Poker with your Jira instance to seamlessly import stories from your Scrum boards. This integration allows you to pull in your backlog items directly, making sprint planning more efficient.

Note: Currently supports Scrum boards only, as they are specifically designed for story point estimation.

Step 1: Generate a Jira API Token

  1. Log in to your Atlassian account at https://id.atlassian.com
  2. Navigate to Security → API tokens
  3. Click "Create API token"
  4. Give your token a descriptive label (e.g., "Pointing Poker Integration")
  5. Click "Create" and copy the token immediately - you won't be able to see it again
  6. Important: Save this token in a password manager (like 1Password, LastPass, or Bitwarden) for safekeeping

⚠️ Security Note: For your protection, pointing-poker.io never saves your API token. You'll need to enter it fresh for each new session, so having it stored in a password manager makes this quick and easy.

Step 2: Required Permissions

Your API token needs the following scopes to work with Pointing Poker:

  • read:jira-work - Read projects, issues, boards, and sprints
  • write:jira-work - Update story points on issues

For standard API tokens, these permissions are included by default based on your Jira user permissions. If you're using a scoped API token for enhanced security, make sure to select these specific scopes when creating the token.

Step 3: Configure in Pointing Poker

  1. Open your Pointing Poker room
  2. Click on the Jira Integration toggle
  3. Enter your Jira instance URL (e.g., https://yourcompany.atlassian.net)
  4. Enter your Jira project key (e.g., "MYPROJECT")
  5. Enter your email address associated with your Jira account
  6. Paste the API token you generated in Step 1
  7. Click "Fetch Projects" to retrieve a list of projects to choose from
  8. Select your desired project from the dropdown
  9. Click "Connect to Jira"
  10. If successful, you'll see a confirmation message and can now import stories

Step 4: Import Stories

  1. Select your Scrum board from the dropdown
  2. Choose the sprint or backlog you want to import from
  3. Click "Fetch Issues" to load stories from Jira
  4. Select the stories you want to estimate (or select all)
  5. Click "Import X Issues" to add them to your session

Troubleshooting

Connection Failed

  • Verify your Jira URL is correct (include https://)
  • Ensure your API token hasn't expired
  • Check that your email matches your Jira account

No Boards Available

  • Confirm you have access to at least one Scrum board
  • Verify that your project uses Scrum methodology (story points are not available in Kanban boards)
  • Check your Jira permissions for the project

Stories Not Loading

  • Ensure the sprint has stories assigned
  • Verify you have permission to view the issues
  • Try refreshing the connection

Still Having Trouble?

If you're still experiencing issues with the Jira integration, we're here to help! Reach out to us with your specific issue and we'll get back to you as soon as possible.

🔒 Security & Privacy

Security-First Approach

Your API token is never saved. For maximum security, you'll need to enter your Jira API token fresh each time you start a new session on pointing-poker.io.

💡 Pro Tip: Store your Jira API token in a password manager like 1Password, LastPass, or Bitwarden for quick and secure access whenever you need it.

How it works:

  • No persistent storage: Your API token is only held in memory during your active session and is never written to disk, databases, or browser storage.
  • Secure transmission: All communication between your browser and Jira uses HTTPS encryption protocols.
  • Backend proxy: Your browser communicates with our secure backend, which proxies requests to Jira's API on your behalf, keeping your credentials protected.
  • Minimal data collection: We only fetch the story information you explicitly request and never access other Jira data.
  • Full control: You can disconnect the integration at any time, and no trace of your credentials remains on our systems.

This security-first approach protects your Jira credentials from unauthorized access, even in the unlikely event of a security breach. While it requires re-entering your API token for each new session, this trade-off ensures your sensitive credentials are never at risk.