Is it possible to exclude the sprint field from cloning

Currently it doesn’t seems possible to exclude the sprint field from cloning, but this would be the best solution, since a sprint is planned within the sprint planning and is not used for defining by reporters.

The next problem is, that currently it is not possible to remove closed sprints by editing the issue. The only workaround provided by Atlassian is to use the bulk operation and remove the sprint id. But this is just a workaround and needs to be handled with care.

 

Thanks for any help or suggestions.

 

2 answers

1 accepted

0 votes
Accepted answer

Out of the box no, it is not possible to purge the sprint field from getting cloned. Clone operation clones everything including Sprint.

You will need to re-write the entire clone operation again to include such a functionality

Rahul

Atlassian has commented my issue:

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

with

Thanks for your suggestion. I'll redirect you to

https://jira.atlassian.com/browse/GHS-6541

as we have a number of customers requesting this feature change.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,653 views 18 21
Read article

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