Jira
otherOverview
The Jira connector links RunMyProcess workflows with the issue tracking your technical and project teams already use. A process can create an issue, update it and search issues, so a request that needs engineering, IT or project work becomes a ticket with the right data, and its progress flows back into the business process that is waiting for it.
This closes the usual gap between business requests and delivery: nobody retypes a request into Jira, the ticket carries the context of the case, and the workflow can check its state or update it when the business side changes something.
Common use cases
- Create a Jira issue automatically when an approved request needs IT or engineering work.
- Update the issue when the requester adds information or the priority changes.
- Search issues to report on the status of all requests from one department or customer.
- Resume the business workflow when the related issue is resolved.
Available Connectors
Security & Compliance
This integration is verified by RunMyProcess and supports OAuth2 authentication. Data is encrypted in transit and at rest.
Frequently asked questions
What can the Jira connector do in a RunMyProcess workflow?
+
It creates issues, updates them and searches for existing ones. Each operation is a step of the process, so work that starts in a business workflow lands in the project where the delivery team tracks it.
Can a business request become a Jira issue automatically?
+
Yes. Once a request is approved, the workflow creates the issue with the data captured in the form, and later steps can update it as the request moves forward.
How does a workflow avoid creating duplicate issues?
+
Search Issues lets the process look for an existing issue before creating one, so a repeated request updates the issue already open instead of adding a second one.
Need help connecting your systems?
Our integration team can help you map this connector into your existing workflows.