What are the options to automate Jira User story creation from the data in the Confluence page

[Amith V R]

What are the options to automate Jira User story creation from the data in the Confluence page?

[John Funk · Accepted solution]

Hi Amith - Welcome to the Atlassian Community!

I suggest you give Rovo a try from the Confluence page. Navigate to the Confluence page, click on the blue Create button at the top of the page, and then select Create with Rovo. 

Then have a conversation with Rovo about what you are trying to do. 

[Arkadiusz Wroblewski]

@Amith V R 

You get some really good advice here if you wanna give Rovo a try. Actually, Rovo is becoming more powerful lately in your specific situation and overall.

[Amith V R]

Hi  @Arkadiusz Wroblewski / @John Funk 

Thank you for replying to my concern. Please find the below problem statement which I am working on.

We are building an automation that generates a Jira User Story directly from a structured Confluence page. The Confluence page acts as a single source of truth containing:

• Project metadata (project key, issue type, priority, epic link, labels, fix version)
• Configuration change details (expected vs. current state)
• A validation plan (step-by-step test scenarios)

The automation constructs a "Create Issue" URL (CreateIssueDetails!init.jspa) with pre-populated fields so that clicking the link on the Confluence page creates a fully-formed Jira Story without manual data entry. US is created through a trigger action eg: Confluence page status change / Button etc.

Why Automation Is Needed

1. Repetitive manual work — Teams repeatedly copy-paste the same data from Confluence into Jira when raising stories for configuration changes. This is error-prone and time-consuming.
2. Data consistency — Field values (epic link, labels, fix version, description) must stay in sync between the documentation page and the Jira issue. Manual creation leads to drift.
3. Standardisation — Each story must follow a consistent structure (scope, config delta, validation steps, acceptance criteria). A templated automation enforces this.
4. Volume — Multiple configuration stories are raised per sprint; automating creation saves significant effort at scale.

[Arkadiusz Wroblewski]

@Amith V R 

Personally, I’d recommend a setup that combines the best of both tools. You can use Rovo on the drafting side, as it's perfect for helping you summarize rough ideas or polish the initial text. From there, you should stick to native Automation or the REST API for the actual issue creation, which gives you a reliable, predictable process for the technical field mapping. For Repetitive Tasks Rovo is still too Unpredictable.

The whole process will work best if you build it around a strict Confluence template to ensure you always capture the exact data you need from the start. Finally, make sure to write the Jira key back to the page immediately after creation.

Storing that issue key directly on the Confluence page is the easiest way to act as a natural lock, completely preventing anyone from creating duplicate tickets by accident. Duplicates are really something you wanna avoid here.

[Amith V R]

@Arkadiusz Wroblewski 

Thanks for the update, If possible if there are any documentation for this can you please provide. It would be of great help

Thanks

[Arkadiusz Wroblewski]

@Amith V R 

there’s no single Atlassian doc for this exact end-to-end setup, but you can  piece it together.

On the Confluence side, you’ll want to use a page status change or manual trigger or even a smart button along with smart values to grab the page data. For creating the Jira issue, the native "Create work item" action in Jira Automation is the easiest route. If you need advanced field mapping, you can use a "Send web request" action in Confluence to hit the Jira REST API instead.

Just remember the API requires fields to be on the create screen and uses Atlassian Document Format (ADF) for text fields.

You also need fairly broad permissions on both sides, and I would not recommend doing this on a Free subscription.

automation in Confluence | Cloud automation Cloud | Atlassian Support

Create Jira issues directly from Confluence with t... - Atlassian Community

Triggers in Confluence automation | Cloud automation Cloud | Atlassian Support

Jira automation actions | Cloud automation Cloud | Atlassian Support

The Jira Cloud platform REST API

[Arkadiusz Wroblewski · Accepted solution]

Hello and welcome to the Community @Amith V R 

The best approach here really depends on two main things:

how your data is currently structured on the Confluence page? and whether you want these stories created completely automatically or with a manual review step first ?

[Arkadiusz Wroblewski]

@Amith V R 

For this, you need to piece everything together as mentioned above. There will be a lot of "Try and Fail", that I am sure of.

[Monika Ambrozowicz_Seibert_]

Hi @Amith V R I agree Rovo will likely get you there. Having said that, I'd like to suggest an alternative solution if you are open to using marketplace apps. The main reason is that they don't require any complex setup and they're easy to use for everyone, including non-technical users for whom dealing with automation is cumbersome. Full disclosure: I am affiliated with the teams behind these apps. 

If the goal is making it fast and consistent for people to create User Stories directly from a Confluence page — say, from a requirements doc, meeting notes, or a product spec — then a Marketplace app called Viable Issues fits that use case well.

Viable Issues lets you embed "Create Issue" buttons anywhere on a Confluence page with fields like project, issue type (User Story), labels, and epic link already pre-configured. When a team member reads the page and wants to turn a requirement into a ticket, they click the button and the issue is created instantly - no full Jira dialog, no manual field selection every time. 

As @Arkadiusz Wroblewski suggested, regardless the solution you choose (Rovo, Jira Automation, Viable Issues), you need a well-structured Confluence template to make sure you always capture the data correctly. Here I would like to suggest another app - Properties - that allows to create reusable Property Groups to capture information like owners, statuses, or deadlines in a way that enforces consistency across pages and spaces. With structured fields like drop-downs, multi-select options, and user mentions, the data stays clean and usable - for example, as a part of a Jira Automation workflow. 

In the screenshot above you can see the property group built with Properties to keep track on new employees, as well as the button created with Viable Issues to create a Jira ticket from this Confluence page. 

If you have any questions, I'd be happy to help.