It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

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
Published in Marketplace Apps & Integrations

Marketplace Spotlight: Manage your assets with asset management apps

  The role of IT professionals has become increasingly difficult over the last decade. Our organizations work in an increasingly software-powered world and IT professionals are expected to not...

295 views 3 9
Read article

Community Events

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

Events near you