The problem began yesterday when a automation that always worked normal begin to result in a error, when i look the log the cause of the error is: "Due date: Due date is required", but we don't use due date in any issue on the two projects where the integration happen.
I test in other classic projects the automation and the problem is the same, the strange part is until yesterday nothing like this happened. This is a bug or now exist a new configuration that don't let a issue from a next-gen project be copy for a classic project?
Hi @Adenilson Aparecido Gomes Junior -- Welcome to the Atlassian Community!
What appears to be happening is that the target classic project requires the Due Date field. You could test that by creating a test issue in the classic project and seeing if the field is indeed required.
If this is the case, consider what recent changes you and any other site admins for your instance have made about the Due Date field.
This morning, Atlassian announced the acquisition of ThinkTilt , the maker of ProForma, a no-code/low code form builder with 700+ customers worldwide. ThinkTilt helps IT empower any team in their or...
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