Skip to main content

​
Pre-Built Tooling

CategoryDetails
AuthenticationBasic Auth (Email & API Token)
Two-Way SyncNo
Events SupportedNo
RealtimePolling
Supports Rate LimitingYes
Authentication Scopes SupportedN/A (Basic Auth with API Token)

​
Objects Supported

Alloy Automation supports syncing the following objects from Jira:
  • Issues
  • Labels
  • Plans
  • Projects
  • Status
  • Tasks
  • Users

​
Set Up Guide

​
Trial Access

QuestionAnswer
Offers free trial?Yes. Jira Cloud offers a free plan for up to 10 users.
Requires paid sandboxNo. The free plan can be used for development and testing.
Requires partnership to obtain authentication?No. Anyone can create a Jira Cloud account and generate API tokens.

​
Authentication (Basic Auth with API Token)

Jira Cloud uses Basic Authentication with your email address and an API token.

​
How to obtain your API Token

  1. Create a Jira Cloud account at https://www.atlassian.com/software/jira
  2. Log in to your Atlassian account (https://id.atlassian.com)
  3. Navigate to Account Settings > Security
  4. Click Create and manage API tokens
  5. Click Create API token
    • Give your token a descriptive label (e.g., “Alloy Automation Integration”)
    • Copy the generated token immediately (you won’t be able to see it again)
  6. Configure credentials in Alloy Automation:
    • Username: Your Atlassian account email address
    • Password: The API token you just generated
  7. Identify your Jira domain: Your Jira site URL (e.g., yourcompany.atlassian.net)
    • The domain part (e.g., yourcompany) will be used as the {domain} variable in API calls

​
API Documentation

​
Use Cases

​
1) Automated issue creation and tracking

Automatically create Jira issues from external systems like customer support tools, monitoring platforms, or incident management systems, ensuring all issues are tracked in a centralized location.

​
2) Project and sprint synchronization

Sync Jira project data, sprint information, and workflow states to project management tools, reporting dashboards, or data warehouses for cross-platform visibility.

​
3) Engineering metrics and analytics

Pull issue data, status transitions, and assignment information to calculate development velocity, cycle time, and other engineering metrics for performance analysis.

​
4) Cross-platform task management

Integrate Jira issues with other task management tools, enabling teams to work in their preferred platforms while maintaining a single source of truth in Jira.

​
5) Automated workflow orchestration

Trigger automated workflows based on Jira issue changes, such as notifying stakeholders when issues reach specific states, updating external systems, or creating follow-up tasks.

​
API Gotchas

  • Domain variable required: Jira Cloud API URLs include your site’s subdomain (e.g., yourcompany.atlassian.net). You must configure the {domain} variable correctly when setting up the integration - using an incorrect domain will result in 404 errors.
  • API token vs password: Never use your Atlassian account password for API authentication. Always generate and use API tokens. Tokens can be revoked independently without changing your password and provide better security.
  • Issue key formats: Jira issue keys follow the format PROJECT-123 (project key + numeric ID). When creating or updating issues, ensure you use the correct format and that the project key exists in your Jira instance.
  • Custom fields: Jira projects often have custom fields with IDs like customfield_10001. These IDs are instance-specific and vary between Jira sites. You must query the field metadata API to discover custom field IDs for your specific instance.
  • Bulk operations limits: When performing bulk operations (create, update, delete), Jira imposes limits on the number of items per request. Typically, you can process up to 1000 issues at once, but check the specific endpoint documentation for exact limits.
  • Pagination: List endpoints use different pagination mechanisms. Most use startAt and maxResults parameters. Always check for isLast or total fields in responses to determine if more pages exist.
  • Rate limiting: Jira Cloud enforces rate limits per user and per app. When you hit rate limits, you’ll receive a 429 response. Implement exponential backoff and respect the Retry-After header.
For questions or troubleshooting, contact support@runalloy.com.
⌘I