I have a template Jira issue with five action items in the description. There's an automation that clones this template issue and runs fine with the exception of changing the action items into bullet points.
If I just manually clone the issue, the action items remain and are properly cloned. For some reason they get changed to bullet points during automation. The automation log shows no issues when run.
Any thoughts on how to troubleshoot this?
Hi @Josh Allen
If you're open to Marketplace add-ons, check out Issue Templates for Jira by Deviniti (the company I work for). It could help with your use case because, instead of relying on Jira Automation's native cloning (which sometimes alters formatting like action items or checklists), you can create and apply issue templates that fully preserve the formatting. When using Issue Templates for Jira to create issues, your checklists, action items, and rich-text formatting will remain exactly as defined in the template, even when triggered automatically. This is a link to the aps's Support Center where you'll find an interactive demo and more information
Hi @Josh Allen
As an alternative to Automation (that can be really complex sometimes), I can suggest trying our app Elements Copy & Sync. It allows you to clone Jira issues while keeping the exact same issue format. You can clone any type of issue field and synchronize the two issues together if needed.
Don't hesitate to check the documentation, it’s really quick and easy to set up.
The app is for free during 30 days (and it stays free under 10 users).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Josh Allen
If you're looking for an immediate solution to clone the description correctly you can try our app Deep Clone for Jira. You can integrate Deep Clone into your Jira automation to streamline repetitive tasks without compromising on detail.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This is a known flaw of the existing capabilities of Jira's action items. The same was addressed in this comment: https://community.atlassian.com/t5/Jira-articles/Introducing-Action-items-in-Jira/bc-p/2888086#M16771 in the original post by Atlassian.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you @Angela Thomas_Seibert Group
Was thinking there might be a known issue out there but wasn't able to find it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.