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?
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Apologies for my tardy response, the success in the log is for when I tried for task but failed for user stories.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
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.