Our users have recurring issues with similar due dates every month. For example: due date is always on the 10th every month. I have created an automation rule that clones the issue on transition from In progress -> Done and sets due date + 1 month.
The automation works well, but the cloned issues are missing the "customer request type" from the previous issue. I can't add this step in the automation rule "since Jira Service Desk does not provide an API for this".
Is it possible to solve my problem in some other way?
Welcome to Atlassian Community!
The Automation (former Automation for Jira) has a limitation when it comes to Request type as you mentioned.
In this case, while this functionality is not implemented, the workaround would be using the Legacy Automation, where there is an action to update the request type.
I tested here creating a simple automation to clone an issue and the request type is empty on the cloned ticket, the same as you mentioned that happens on your site, but using the rule below, it will update the field as soon as the cloned ticket is created:
Please, give it a try and let us know how it goes.
We often have questions from folks using Jira Service Management about the benefits to using Premium. Check out this video to learn how you can unlock even more value in our Premium plan. &nb...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events