Ticketing integrations: Set up for procurement (Asana, Jira, Linear)

Overview

Use Ramp’s ticketing integration to create and track procurement tasks in Asana, Jira, or Linear. Add a ticketing step to any procurement program so each request creates a ticket with key request details. You can choose whether the workflow waits for the ticket to be completed or continues right after creation.

What you can do

• Connect Asana, Jira, or Linear from the Integrations tab
• Auto-create tickets from procurement requests
• Select the target project or team
• Add a title prefix, assignees, and tags
• Include request details and custom instructions in the ticket
• Control when the Ramp step is marked complete (on creation or on completion)

Requirements

• Ramp admin or program editor permissions
• Admin or sufficient permissions in the target ticketing tool to connect the app and create tickets
• An existing project/team/board in Asana, Jira, or Linear

Connect a ticketing app

Step 1: In Ramp, go to the Integrations tab

Step 2: Open the Productivity category.

Step 3: Select Asana, Jira, or Linear.

Step 4: Click Connect app and follow the on-screen instructions for that tool.

Add a ticketing step to a procurement program

Step 1: In Ramp, go to Procurement > Programs.

Step 2: Create a new program or open an existing one (for example, a Purchase Order program).

Step 3: Add a new step (node) to the workflow.

Step 4: Choose the ticketing tool you connected (Asana, Jira, or Linear).

Configure the ticket

Step 1: Select the project/team/board where the ticket should be created.

Step 2: Add an optional title prefix (for example, “Testing”).

Step 3: Add assignees from your Ramp instance.

Step 4: Add tags if you want them applied to the ticket.

Step 5: Write a description for the ticket. You can:

• Add custom instructions for your employees
• Attach details from the Ramp request so the ticket includes key request info

Choose when the step completes in Ramp

Step 1: Set the approval behavior for the ticketing step:

• Open: Non-blocking. Ramp moves to the next step as soon as the ticket is created.
• Closed: Blocking. Ramp waits until the ticket is completed before moving to the next step.

Save and test

Step 1: Click Save to update the program.

Step 2: Submit a test request using the program.

Step 3: After submission, open the ticket URL shown in the step to view the ticket in Asana, Jira, or Linear.

Step 4: If the step is set to Closed, complete the ticket in the tool to let the workflow proceed.

Tips

• Use a clear title prefix (for example, request type or vendor) to make tickets easy to search.
• Include key request fields in the description so approvers and collaborators have full context.
• Assign the step to the right team to avoid delays.

Troubleshooting

• I don’t see my project/team: Confirm you connected the correct workspace and have access in the ticketing tool.
• Ticket not advancing the workflow: If the step is set to Closed, make sure the ticket is marked complete in the tool. Recheck the status mapping if your tool uses custom states.
• Assignee not available: Assignees must be users in your Ramp instance. Make sure the user exists and has access.
• Duplicate tickets: The step creates one ticket per request run. Avoid retrying the entire request if the ticket already exists. Instead, open the linked ticket or re-run only the step if available.

Notes

• Each ticketing tool may show slightly different fields during setup.
• You can connect more than one tool. When adding the step, pick which tool to use for that program.