Deep clone not cloning time tracking

Joanna Richter
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
March 14, 2024

When I do a deep clone of a filter, the time tracking that I have assigned to each task does not clone. Is there a way to clone these details?

2 answers

1 accepted

2 votes
Answer accepted
Luka Hummel - codefortynine
Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
March 20, 2024

Thank you for reaching out to us @Joanna Richter (and welcome to the Atlassian community)

I will post our findings here, so other community members with the same question might find the solution faster 😊

In your case, you had set a Remaining estimate value without any work logs present, and no value set for Original estimate.

Unfortunately, there are API limitations in Jira that don’t allow us to set the Remaining estimate value without a work log present. We have now documented the limitations correctly in our documentation.

A workaround is setting the Original estimate value to your Remaining estimate value via a Jira automation before cloning the issues. After cloning, the Remaining estimate value will be the Original estimate value of the original issue.

2024-03-20 13-32.png

1 vote
Stephen Wright _Elabor8_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 17, 2024

Hi @Joanna Richter 

I'm not sure why this would be happening, but perhaps it would be best to contact the vendor for assistance?

You can see their contact details on their Marketplace listing's support tab - see:

Let us know what the answer is!


Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events