nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Save task description to Confluence

Oleksandr Suprun

Hi all,
So I have an idea that I'm not able to fulfill on my own.

I'd like to save tickets description to a confluence page upon transition.
So, I can have some kind of technical documentation stored automatically

For example when I move my tickets from IN PLANNING to TO DO
then on this trigger, a confluence page would be created with the ticket's title and description.

I was trying to solve this issue via Jira automation as it allows to crate confluence pages on triggers, but I got no clue how can I transfer the description.

Or should I set up a specific template in confluence?

I'd appreciate any thoughts

Thanks in advance

Accepted answers

Julia Foden

HI @Oleksandr Suprun

See the answer on this page https://community.atlassian.com/t5/Automation-articles/Automation-feature-roundup-Permissions-forms-and-connections/ba-p/2073728

I had asked about adding content from the Jira ticket to the page body but the answer was

"Currently, adding content to the page body isn't possible, because all the action does is create the page; it doesn't touch the content itself. But this is good feedback, and we'll certainly take it on board and think about it."

All comments

Dave Mathijs

Hi @Oleksandr Suprun , interested to know why one would like to copy the description of a Jira issue to a Confluence page.

Oleksandr Suprun

Well for me - Confluence is a much more convenient way to store project documentation rather than just keeping it in the Jira tasks

So I wonder if there is a possibility to copy tasks description automatically to Confluence.

Walter Buggenhout

Hi @Oleksandr Suprun,

You are totally right about Confluence being a better place for documentation. That is why it is a very common scenario that requirements often get documented in Confluence first and Jira issues get created afterwards.

I took the effort to create a full example of what that might look like:

An-Epic-requirement-Confluence-Demo-Space-Confluence.png The idea is that you start in Confluence instead of Jira. Create a single page for each epic and add your story summary and description in a table (1 row for each story).

If you make sure to create your Epic in Jira and link it to your Confluence page, you will be able to create Jira issues in bulk an link them to your Epic, using 2 columns from your table as summary and description:

Screenshot 2022-07-17 at 14.23.33.png

The actual text in my first screenshot describes the steps to do all this.

This is the Epic in Jira, with all linked stories. I did not type a single word in Jira to create all this, just created all the issues from my Confluence documentation:

Screenshot 2022-07-17 at 14.31.29.png

Hope this helps!

Oleksandr Suprun

Thanks for your answer. That's kinda the way we are doing it right now. I was wondering if this can be done the other way around.

Julia Foden

HI @Oleksandr Suprun

See the answer on this page https://community.atlassian.com/t5/Automation-articles/Automation-feature-roundup-Permissions-forms-and-connections/ba-p/2073728

I had asked about adding content from the Jira ticket to the page body but the answer was

Oleksandr Suprun

Thank you so much for this clarification.
Now we only have to wait

Julia Foden

@Oleksandr Suprun a workaround would be to use the action "Send Web Request" to send a call to the Confluence API. I tested this a while back and it worked, including adding data from the Jira issue into the body of the page. I was putting it into a table but didn't go any further into testing page layout. See https://developer.atlassian.com/cloud/confluence/rest/api-group-content/#api-wiki-rest-api-content-post

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

confluence

jira

cloud

jira-software

jira-software-cloud

automation