Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

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

Don't want to copy field value to cloned issues

SM I'm New Here Dec 11, 2020

I have created a mandatory field in my project. I want when I clone the tickets this field value should not be copied to the new ticket.

-When we clone the ticket we see a summary field, I want this field as well on the same screen. 

For ex- I have created a new mandatory field as Regions and it has options Asia
Europe and America. When I clone the issue the value of this field should not copied.

 

3 answers

0 votes
DPK J Community Leader Dec 11, 2020

@SM Welcome to the community!

I don't think this is possible with vanilla Jira.

I think plugin ScriptRunner can help you here.

0 votes
Daniel Ebers Community Leader Dec 12, 2020

Hi SM,

welcome to the Atlassian Community.

For a very similar requirement we successfully used "Clone Plus" App (Appfire) from Marketplace.
Possibly there are similar Apps available meanwhile - you would have to check through https://marketplace.atlassian.com

Even if you decide to go with Clone Plus be noted this App needs extra payment - but you can test using a trial if it meets your needs.
From what you wrote this is absolutely doable.

Cheers,
Daniel

Welcome to the Community, @SM !

Is the field also mandatory in the target project you want to clone into? If yes, that could be a problem, because the fields needs to have a certain value when the cloned issue is created.

With your Jira cloud app Deep Clone for Jira, you could either

  • Configure your clone in a way that certain fields aren't cloned.
  • "Create and confirm" your clone, to edit it before the cloned issue is created.
  • Update fields automatically when the clone is created, using "auto-edit fields".

If you have questions or feedback about Deep Clone for Jira, don't hesitate to get in touch with our support.

deep-clone_single-clone-dialog.png

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Continuous Delivery

Our Atlassian Partners continue to support their customers during coronavirus pandemic

Across the world, governments and healthcare authorities are demonstrating the power of collaboration to find solutions to the COVID-19 pandemic, to protect our communities, and to get things back to...

1,625 views 1 13
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