Trying to automate cloning user stories from a project to a kanban board
Asked by Chukwuma Ezeh:

I was able to automate cloning from a scrum board to kanban board for tasks but that for user stories keeps failing. Is there a way around this?

[@Bill Sheboy](/t5/user/viewprofilepage/user-id/1685313)

![image.png](/t5/image/serverpage/image-id/347568iBB55D86632C57DC8/image-size/large?v=v2&px=999 "image.png")


Answers:
author: Bill Sheboy
body: Hi [@Chukwuma Ezeh](/t5/user/viewprofilepage/user-id/5593563) -- Welcome to the Atlassian Community!

What do you observe happening when the rule does not work as expected for Story issue types?

Please post an image of the audit log details showing the rule execution.

Kind regards,  
Bill

comments: author: Chukwuma Ezeh
body: ![image.png](https://community.atlassian.com/t5/image/serverpage/image-id/347936i0030FB39F0E710CD/image-size/large?v=v2&px=999 "image.png")


author: Chukwuma Ezeh
body: Apologies for my tardy response, the success in the log is for when I tried for task but failed for user stories.


author: Bill Sheboy
body: Please retest your rule without further changes. And then...

At the right side of the log, please select the **Show more** option to display the details for one of the failures when the rule runs for a Story. Then post an image of that log entry.


author: Chukwuma Ezeh
body: ![image.png](https://community.atlassian.com/t5/image/serverpage/image-id/348097i424EA78663A2AC9A/image-size/large?v=v2&px=999 "image.png")


author: Bill Sheboy
body: What are the types of project for the trigger issue and the one into which you want to clone: company-managed or team-managed?

If they are team-managed, the issue types, fields, and other configurations are unique for the projects. And so the Clone Issue action cannot match up the fields, even when they have the same names.

In that case, the clone action will need to select the specific fields and copy the values from the trigger issue, or use advanced edit with JSON to set them using the custom field id values: <https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/>


author: Chukwuma Ezeh
body: The trigger issue has Epic, Story, task and sub-task while the destination project has Epic, task, sub-task; both are tam-managed.

The custom field ID is a bit confusing but will take more look at it and revert


author: Luka Hummel - codefortynine
body: Hi [@Chukwuma Ezeh](/t5/user/viewprofilepage/user-id/5593563) and welcome to the community!

To efficiently automate cloning user stories, our app [Deep Clone for Jira](https://marketplace.atlassian.com/apps/1218652?utm_source=atlassian&utm_medium=referral&utm_campaign=deepj-new-reach-com-2813238) could be a perfect solution. It allows you to clone entire issues, including user stories, across projects with ease. You can set up automation rules that clone not just tasks but also stories without manual intervention. Read more on that [here](https://documentation.codefortynine.com/deep-clone-for-jira/jira-automation?utm_source=atlassian&utm_medium=referral&utm_campaign=deepj-new-reach-com-2813238).

You can also configure the fields precisely, using the [Field Editor](https://documentation.codefortynine.com/deep-clone-for-jira/field-editor?utm_source=atlassian&utm_medium=referral&utm_campaign=deepj-new-reach-com-2813238) feature, ensuring the cloned stories retain key information.

Deep Clone handles both team-managed and company-managed projects.


Tags: cloud

jira-cloud