• Community
  • Discussions
  • Defining clone pre-fixes at point of cloning (ie "story" or project specific - not global settings)

Defining clone pre-fixes at point of cloning (ie "story" or project specific - not global settings)

Jo Bland I'm New Here Nov 02, 2017

Hi there,

We use JIRA both for projects & developments as well as data operations across 4 countries where we run regular stories for operational needs - such as onboarding new customers, releasing a new cycle of data in our live products.  At the moment the clone prefix is a global setting so we have a generic prefix of (CLONE) which we then have to rename every time for either a new period of data or a new customer name.

Ideally I would like to set my clone prefix for all sub tasks at the point of cloning to save loads of time manually editing up to 25 sub tasks each time eg all sub tasks are prefixed with "Jan 2017 release" or "Customer1".

Is this anywhere on the product roadmap to do?

Many thanks

Jo

0 comments

Comment

Log in or Join to comment
Community showcase
Monique van den Berg
Published Thursday in Feedback & Announcements

How to earn badges on Atlassian Community

You may have visited your profile and seen a tab called badges. (If not, click on your avatar and View profile > Badges will get you there.)  But what do the happy little circles mean,...

226 views 4 8
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
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot