When cloning an issue any associated dates (start, end and due dates) are also cloned as they are.
This can result on cloning start dates and end dates in the past - surely these should be cleared?
Additionally, surely the due date should be adjusted to reflect the new occurrence's month?
Actually this is an expected behavior, as the Clone function copies the entire issue. We have a feature request raised to allow more cloning options and to allow users choose fields to be cloned or not. Please find the feature request on the link below:
Alternatively, you can consider using this plugin to have more options when cloning issues.
-- Arthur Gonçalves
Thanks Arthur. While it makes sense that this is the default behavior for JIRA, it is not what we would expect from a recurring issue plugin as it makes no sense to clone new issues with past due dates (as everything appears overdue). Probably one for the plugin developers rather than JIRA.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Confluence Data Center is a deployment option that was designed for performance at scale. In other words, Confluence will handle increased traffic much reliably in a clustered environment and yo...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs