Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Trying to automate cloning user stories from a project to a kanban board

Chukwuma Ezeh September 16, 2024

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 

image.png

2 answers

1 vote
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 16, 2024

Hi @Chukwuma Ezeh -- 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

Chukwuma Ezeh September 18, 2024

image.png

Chukwuma Ezeh September 18, 2024

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

Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 18, 2024

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.

Chukwuma Ezeh September 19, 2024

image.png

Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 19, 2024

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/

Chukwuma Ezeh September 19, 2024

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

0 votes
Luka Hummel - codefortynine
Atlassian Partner
September 23, 2024

Hi @Chukwuma Ezeh and welcome to the community!

To efficiently automate cloning user stories, our app Deep Clone for Jira 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.

You can also configure the fields precisely, using the Field Editor feature, ensuring the cloned stories retain key information.

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

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events