There is a new feature that allows the setting of the Due Date field to "recur" in intervals, such as "Recurs weekly".

For users trying this feature for the first time, it is confusing as to what this feature does. One could think that it would change the Due Date in set intervals, but it does not do this.

When a user sets a Due Date to recur, it actually creates a read-only Automation rule in the background (unknown to the user). The logic of the rule is to clone the Work Item on a schedule.

Many users would not be expecting this kind of logic. They would need to look up Automation rules manually to know this exists. As well, if done for multiple Work Items. there can be a long list of rules called "Clone on a schedule" with no way to differentiate these/know which Work Items they are associated with.

The existing documentation also does not make it clear that this also applies to "Due Date" (besides a small reference at step 2:

• https://support.atlassian.com/cloud-automation/docs/automatically-clone-an-issue-when-done/

Another reference to this feature:

• https://community.atlassian.com/forums/Jira-Service-Management/Re-Function-Due-Date-quot-Set-to-recur-quot/qaq-p/3014230/comment-id/206058#M206058