Possible Bug / Feature Request

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?

2 answers

1 vote

Hello Lee,

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:

https://jira.atlassian.com/browse/JRA-5052

 

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.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Oct 11, 2018 in Marketplace Apps

You + one app + a desert island...

Hi all! My name is Miles and I work on the Marketplace team. We’re looking for better ways to recommend and suggest apps that are truly crowd favorites, so of course we wanted to poll the Community. ...

3,057 views 6 6
Join discussion

Atlassian User Groups

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!

Find my local user group

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

Groups near you