Scenario- in jira story out of 10 fields lets say 2-3 fields are redundant and used for all the stories within the project , would it be the right practice to clone the jira or we should create the jira.
Hello John, Thank you for the response, but unfortunately I see some Scrums master are only enforcing the practice of Cloning jira stories as it help there team / product/BAs
Regards,
Snehal
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
For efficiently cloning issues in Jira, you could try our app Deep Clone for Jira. This tool allows you to clone issues, epics, and even complete projects while maintaining all field values, attachments, and comments. It simplifies the process by letting you select exactly what you need to clone, making it an excellent fit for your scenario of copying specific fields across multiple stories.
That decision depends largely on how much data you want to reuse. If you have lots of custom fields that are filled and should stay filled in the new issue, cloning is definitely preferable. With only 2–3 fields being redundant, it might be better to create a new issue and copy the needed values via an automation. Although, this calculation can change with the new redundant fields being added or the type of custom field you are trying to copy. Some fields are easier to copy with automations than others.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Spend the day sharpening your skills in Atlassian Cloud Organization Admin or Jira Administration, then take the exam onsite. Already ready? Take one - or more - of 12 different certification exams while you’re in Anaheim at Team' 25.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.