Log a comment on a Jira ticket
Uses information gathered by the agent to add more context to issues in Jira via comments.
Solutions by app
Jira: Orchestrate work from backlog to delivery, across your stack
With Tray, Jira becomes the governed control plane for enterprise workflows and agents. Issue events and forms trigger secure actions across IDP, ITSM, CI/CD, and CRM, with results written back to Jira to keep teams in sync.
Jira and Tray
Jira is the system of record for incidents, changes, and delivery work. With Tray, every Jira update can trigger governed actions across your stack—approvals in IDP, access changes in ITSM, deployments in CI/CD, or customer updates in CRM. Results write back to Jira automatically, so records stay accurate and teams stay aligned without context switching.
With Tray, you build and that connect Jira across your business systems and teams.
Automations
Integrations
Agents
Automation
Automations with Jira and Tray
Use issue events and forms to route work, capture approvals, and keep systems in sync. Automations post updates back to the record and the right team with a clear audit trail.
Explore Jira-ready templates from Tray’s library
Tap into Tray’s Template Library to deploy proven workflows to your Tray account and run them with Jira for issues, approvals, and updates.
Index unstructured knowledge from Jira
Extract data from their Jira tickets and turn them into Knowledge articles for a support use-case.
Integrations
Integrations with Jira and Tray
Every issue should move the rest of your stack. When an issue is created, updated, or transitioned, Tray calls the right APIs in IDP, ITSM, CI/CD, and CRM, then writes results to the record and posts status to the team. These connections power event-driven automations and the tools your agents use to take action.
Jira integration capabilities
Integrate Jira with 700+ applications plus any system with an API using our HTTP connector. These domains mirror Jira’s REST API and how teams actually work with Jira.
Create/update issues correctly with custom fields and links
- Create and update: Set fields, labels, components, assignees, due dates
- Fields: Manage custom fields with valid values and schemas
- Links and relations: Link issues, epics, and parent-child relations
- Bulk jobs: Bulk operations and pagination for high-volume jobs
Agents
Build agents with Jira and Tray
Make Jira the knowledge and action surface for your agents. Jira events provide live context; Tray turns them into governed triggers. With Merlin Agent Builder, agents act across systems, stay within approved project scope, and write outcomes back to Jira issues with full traceability.
Give agents the Jira context they need to answer accurately
- Project scope: Index selected projects, issues, and fields you authorize
- Linked knowledge: Pull in related docs from your knowledge sources
- Freshness: Schedule re-ingestion and set retention windows
- Scoping: Limit by project, issue types, and field visibility
Tray vs. Atlassian Virtual Agent (for Jira)
Atlassian Virtual Agent is Jira’s native agent option. If most of your processes and data live in Jira, Atlassian Virtual Agent may fit. If you need a Jira agent that operates across the rest of your stack, Tray is the better choice.
Merlin Agent Builder
Runs agents that act in Jira and across your stack, posting outcomes back to the issue and team
Acts through 700+ connectors and any REST API so one agent can coordinate IdP, ITSM, CI/CD, and CRM in a single flow
Enforces cross-system guardrails, RBAC, approvals, and full execution logs across all downstream tools
Deploys in Slack, Teams, web, or email while keeping Jira as the system of record
Atlassian Virtual Agent (for Jira)
Handles handoffs to Jira Service Management workflows and automation rules, including outgoing web requests
Uses intent flows and AI-driven answers to resolve common requests or gather information before routing to agents
Runs on Atlassian Intelligence models managed within the Atlassian platform
Operates in Slack, Teams, the JSM portal, and the help center
FAQs
Tray reads field schemas and permitted values so forms and automations stay valid. For transitions, define required fields per state and validate inputs before calling the transition.
What comes standard with Tray
Whether your systems, data, or models run in the cloud or on-premises, Tray connects them in one secure platform. Every connection, workflow, and agent operates under IT governance with encryption, audit logging, and access controls built in. Security teams can trust that all integrations comply with enterprise network and authentication policies.
Universal connectivity
- Prebuilt connectors: 700+ connectors plus a universal HTTP connector for any REST API
- Custom connectors: Build custom connectors that behave like native ones
- Connect anywhere: Cloud or on-prem systems supported
On-premises connectivity
- Connect securely: Access on-premises systems, whether first-party or third-party
- Meet network requirements: Connect through approved configurations that align with enterprise security policies
- Enterprise protocols: Support multiple on-premises security standards for safe integration
Authentication management
- Secure credentials: Collect and store authentications with full encryption
- Encrypted data: Protect all data at rest and in transit
- Role-based control: Partition credentials by workspace and access level
Security and governance
- Certified compliance: SOC 2 Type II, GDPR, CCPA, HIPAA
- End-to-end protection: Encryption, detailed audit logs, scoped connections, and OAuth scopes