Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Clone issue Post Function - clearing the Original Estimate field for cloned issues


I am at combination of Jira v.7.2 and script runner v.5.3

Previous admins have created a cloning mechanism which creates a new issue coping all the fields from parent issue.

End users now need the Original Estimated field to be purged upon cloning.

Any idea how this may be achieved?

The below lines don't function.

def cf = customFieldManager.getCustomFieldObjects(issue).find { == 'Original Estimate'}
issue.setCustomFieldValue(cf, null)


P.S:I am new here and can't understand how script runner works. Documentation didn't help me either.




0 answers

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted in Jira Service Management

Jira Service Management Documentation Opportunities

Hello everyone, Hope everyone is safe! A few months ago we posted an article sharing all the new articles and documentation that we, the AMER Jira Service Management team created. As mentioned ...

183 views 0 5
Join discussion

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