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; } } }

Cloning action items

Tim Bonney

I have an issue (Issue type = Task) that needs to be cloned and performed annually.

The root issue contains a list of individual actionable tasks. This can be accomplished in one of two ways. Either, including them as "action items" listed out within the description field (which, when choosing "Action item []" from the edit menu when adding the initial description, generates the list with checkboxes in front of each item that can then be ticked upon completion) of the task. Or, by including them within an actual 'Checklist' on a checklist tab, which appears above the activity pane. (The ability to do this appears to be as a result of an add-on called 'Checklist from AppBox'.)

I have been unable to get the checklist tab to generate on the cloned issue at all. I am guessing this is because it appears t be the result of an add-on, but am not sure if I am just doing something improperly.

When trying it as an action items listing in the description (which I do believe to be native Jira functionality and not added functionality form an add-on), it recreates the description, but as a simple bullet list instead of actin items with checkboxes as they appear on the root issue being cloned. (with a "-" appearing in front of the bullet for any of the items that were checked off as completed on the root issue.)

I have yet to be able to find any direction on how to accomplish this task. Has anyone ever done this successfully?

Thank you in advance for any insight you might be willing and able to share.

Accepted answers

Payal _appbox_ai_

Hi @Tim Bonney

We are Appbox; first, thanks for using our Jira Plugin.

There are two solutions to your query.

Solution 1) As suggested by @Marc -Devoteam- - you can use the Jira Deep Clone plugin. This is because our checklist data is completely stored inside the Jira ticket as Issue Properties but due to an existing Jira Bug, when you clone the Jira Issue, the issue properties don't get cloned. Deep Clone solves that.

Solution 2) Use our Template Assignment feature, where you can insert this checklist template when a specific type of issue is created. We strongly believe this should be your go-to solution since you will have full control over which Task tickets should get what template.

https://docs.appbox.ai/checklist/assigning-templates

If you face any issues in doing this, reach out to our Global Service Desk team for assistance support@appbox.ai

Thanks,

Team Appbox.

All comments

Marc -Devoteam-

Hi @Tim Bonney

The option with the 3rd party app won't work as this is a 3rd party app and this app would need to support such an action. The default clone option from Atlassian doesn't take apps in to account

The other option is failing as when cloning the description is seen as text, I presume you use automation for this action.

Automation doesn't render markup/markdown.

You could look to try a 3rd party app "Deep clone", it that would solve your issue.

Tim Bonney

Thanks for the feedback @Marc -Devoteam-

Payal _appbox_ai_

Hi @Tim Bonney

We are Appbox; first, thanks for using our Jira Plugin.

There are two solutions to your query.

https://docs.appbox.ai/checklist/assigning-templates

If you face any issues in doing this, reach out to our Global Service Desk team for assistance support@appbox.ai

Thanks,

Team Appbox.

Tim Bonney

Thank you @Payal _appbox_ai_

I went to the AppBox site and found solution # 2 and was actually already testing it out when you replied. I believe this is going to work out well for what I am attempting to accomplish. Thanks again.

Payal _appbox_ai_

Thanks @Tim Bonney - we are glad it worked out for you. 🤗

Tim Bonney

@Payal _appbox_ai_

The way I got this to work was to create a template and assign it to the specific type of issue I am working with here. Once I clone the original issue, the templated checklist does successfully get added to the newly cloned issue.

However, since it is the Appbox plugin we're using for the checklist feature, can you please advise whether or not there is a way to update/replace text within the checklist after the fact (through automation), updating all references to calendar years? (ie: change all 2025 to 2026 and all 2026 to 2027, etc.)

Or, must we manually go into and update the template each year, prior to generating the cloned cases?

Thanks in advance.

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management