How to replace version field in projects with one global version field

Answered

Hi everybody,

in the past every of our projects had their own release cycle and therefore had it's own version field. By now they all share the same release cycle and therefore have the same release version maintained. What's the best way to get rid of the seperate Version fields and replace it with one global one, without loosing the information that has already been maintained?

Thanks in advance

2 comments
Comment actions Permalink
Official comment

Hello Markus, thank you for the question and I'm sorry for the delay.

Here's what you can do:

0) Create a global field that will replace all previous ones

1) In Custom Fields settings > Fields in Projects, expand a project

2) Select a field that is to be replaced.

3) Click the 'Replace' button on the top of the list: http://prntscr.com/ejs35b 

4) Select your global field from the list.

5) Read the notification popup carefully.

6) Do that with all projects where you need version fields replaced

 

After that the values bundle that you were using with your old field will remain the same. If you'd like to merge the sets of values further, use the 'Merge' button in the field settings: https://www.jetbrains.com/help/youtrack/incloud/2017.1/Managing-Sets-of-Values.html#MergeValues

 

Please let me know if you have any further questions. Thank you!

Comment actions Permalink

We achieve this in our sprint process through using "merged" values of a custom field.

Team Alpha may have 3 projects running at a time.

  • Project Bravo
  • Project Charlie
  • Project Delta

What we've done is treat Project Bravo as the SSOT. To do this, you go to the projects > fields section for the other two projects, and navigate to your sprint field (Fix Version... Sprint... whatever). Choose "Merge with" and select the Project Bravo sprint field. Then do the same with Project Delta. You'll now notice that the fields are merged across the projects, and updating the value in one project will update it in all.

We encoutner problems with this creating a new sprint from the Agile Board, but it works fine editing from a ticket.

0

Please sign in to leave a comment.