# Create a new issue in Jira: n8n workflow template

> Started by an event in a connected app, and works across Jira. 2 steps: small enough to read in one sitting and change without fear.

Source: https://millionrounds.com/workflow/create-a-new-issue-in-jira (Millionrounds; every figure on the page links to its filing or article)

[Automation library](https://millionrounds.com/workflows) · [Integrations](https://millionrounds.com/workflows?category=Integrations#library)

# Create a new issue in Jira

Started by an event in a connected app, and works across Jira. 2 steps: small enough to read in one sitting and change without fear.

Small

[Download free](https://millionrounds.com/login?next=%2Fapp%2Fworkflow%2Fcreate-a-new-issue-in-jira)

**2 steps** Small: readable in one sitting

**0** Branches: places the flow splits

**0** Loops or waits

**1** Service it connects to

## The flow

Starts it 1 Service 1

The steps in the order they run, from what starts it.

- 1 **On clicking 'execute'** Manual trigger *Starts it*
- 2 **Jira** Jira *Service*

## How it's built

- **Starts on:** An event in a connected app
- **Steps:** 2
- **Size:** Small: readable in one sitting
- **Connects to:** Jira
- **Model:** None. This is plumbing, not judgement

## Questions

What does it need to run?

An n8n account, plus your own Jira account. You connect your own accounts after importing it; none are included.

What starts it?

It starts on an event in a connected app.

Does it use AI?

No. Every step is fixed logic or a call to a service, so it does the same thing every time.

How long does it take to set up?

Not long. At 2 steps it can be read in one sitting and changed without fear.

How do I import it?

Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.

**Before you run it**

Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 2 steps before you point it at anything that matters.

## Run it in n8n

- **Create your n8n account** Free to start. n8n is where the workflow runs. [Create an n8n account ↗](https://millionrounds.com/n8n)
- **Download the workflow** Free with a Millionrounds account. [Download free](https://millionrounds.com/login?next=%2Fapp%2Fworkflow%2Fcreate-a-new-issue-in-jira)
- **Paste it into n8n** Open a new workflow in n8n and paste. Then connect your own accounts.

Stored with the author's traces removed: canvas notes, instance identifiers, saved credential names and any live document they had left behind.

## Connects to

Each opens the other workflows that use it.

[Jira](https://millionrounds.com/workflows?service=Jira#library)

## Workflows like it

Also integrations, with the same services where possible, closest in size first.

- [**Automate Figma versioning and Jira updates** 3 steps · Jira](https://millionrounds.com/workflow/automate-figma-versioning-and-jira-updates)
- [**Send weekly RAID risk digest emails from Jira** 4 steps · Email, Jira](https://millionrounds.com/workflow/send-weekly-raid-risk-digest-emails-from-jira)
- [**Incident response workflow - Part 3 with Jira and Mattermost** 5 steps · Jira, Mattermost](https://millionrounds.com/workflow/incident-response-workflow-part-3-with-jira-and-mattermost)
- [**Get all parents and sub tasks in Jira sprint** 7 steps · Jira](https://millionrounds.com/workflow/get-all-parents-and-sub-tasks-in-jira-sprint)
- [**Manage custom incident response in PagerDuty and Jira** 14 steps · Jira, Mattermost](https://millionrounds.com/workflow/manage-custom-incident-response-in-pagerduty-and-jira)
- [**Automate GitHub PRs & Jira updates** 15 steps · Jira](https://millionrounds.com/workflow/automate-github-prs-and-jira-updates)