What is the best way to replace a field bundle?

Hi,

We have a field Type. And we've been using the same bundle across all projects. Now we want to separate one project out of the rest, remain existing types for it, but then add a type just for that project.

I was hoping we could create a new bundle and swap the bundle for an existing field. I don't see this to be a direct option. What would you suggest? Creating a new field with new bundle and then copy values for all issues from old field to new? If so, how would I execute such update?
23 comments
Comment actions Permalink
Under the admin user go to the target project > 'Type' field > bundle and use 'Create a copy' action. Please look at the Custom fields reference.
0
Comment actions Permalink
How do I do that for a user[1] type field? Can't find a way.
0
Comment actions Permalink
It doesn't matter what field type do you use, in the project > Fields > field_name > link on the top "create a copy" you can create a copy of this bundle and attach it to the 'Type' field of another project.
0
Comment actions Permalink
Sorry, I wasn't clear: I asked that because I can't see that "create a copy".

I've tried with both field and field bundle, with no success (see attachments).

The only link with "Copy" word is "Copy Users", that only copies the values, in this case: it doesn't allow me to replace the used bundle.
0
Comment actions Permalink
Please look at this screenshot. On the top there is the action 'create a copy'. Don't you have?
copy bundle.png
0
Comment actions Permalink
Apparently my attachments didn't get attached.

I will try again now, by the way no, I don't get that "create a copy" option.
0
Comment actions Permalink
I confirm. Attachments are ignored by the forum: very handy...
0
Comment actions Permalink
Please try do this under the 'root' user.
0
Comment actions Permalink
Same thing as a root.
0
Comment actions Permalink
What do you see instead of the line
"This bundle is used in 4 projects and is default for 1 field. Any change will affect all these projects.You can create a copy of the bundle for project A."?
0
Comment actions Permalink
I figured that "Create a Copy" is available only if a bundle is assigned to fields in more than one project. Otherwise it's not there. I think the assumption is that you can simply edit that bundle, no need to worry about other projects.
0
Comment actions Permalink
I hope you can see at least pasted links:
https://drive.google.com/file/d/0Bwyikk66Ki5LeFdWOUtmRGhjbjg/edit?usp=sharing

Anyway I see only "This bundle is used in 1 project Any change will affect this project". That's all I can see, either with my user (Admin, with basically all privileges) or as root.
0
Comment actions Permalink
I don't want to edit the bundle.

The bundle I want to use is already available and configured.
I want to tell YT to change the custom field bundle from A to B.
0
Comment actions Permalink
I was trying to do the same thing and couldn't. Seems to me that the supposed workflow would be to change that bundle. Would be nice to be able to swap to a different one. Without loosing values if the new one has them.
0
Comment actions Permalink
So, I guess the way to circumvent this limitation, you can create a temp project, assign the field and the bundle to it, then clone the bundle for the original one and kill the temp project. But you won't be able to assign an existing bundle.
0
Comment actions Permalink
That just makes no sense.

If this is really the only solution, I wonder why it took 5 posts in this thread to find out that I just can't do what I'm supposed to be able to do.

Anyway, I imagine I don't have other options.

Thanks Michael.
0
Comment actions Permalink
Sorry, I find a few inconveniences like that in Youtrack. I think they are bugs. Most of the time I report them in the vendor's Youtrack. Very rarely they get fixed. I try to find ways around... Hopefully this helps.
0
Comment actions Permalink
Unfortunately, even your workaround doesn't work: this "create a copy" link really don't want to appear.

Now I have added the field, with the right bundle, to a sandbox project we have there for new users in our company.

Clicking in the bundle of the sandbox project, I'm still getting the same options as before.
Same if I click in the bundle of the real project, of course.

I hope someone from the support can just go in my instance (is an inCloud instance) and fix this: I just can't make our workflow do what it's supposed to do without this fix.
0
Comment actions Permalink
Sorry I couldn't help
0
Comment actions Permalink
If you don't need to save this field values in issues you can just detach this field and reattach it with the new bundle.
If no, please try to 'merge' this bundle with that new created - click on the 'Merge' action in the 'bundle' tab.
0
Comment actions Permalink
Dmitry, the first option is not applicable, as we already have some tickets with this field set to a value.
As for the second option, I don't see how the merge can allow me to change the bundle bound to that field.
0
Comment actions Permalink
The 'merge' action merges two boundles and remains the target one, e.g. your new bundle. The new bundle will be bound to this field.
0
Comment actions Permalink
Ok, this seems to work.
I've lost the old bundle, but since it was used only in another project that is only for testing, it's fine.

Still, I think that this process is cumbersome, non intuitive and really little usable.

Thanks anyway for the help!
0

Please sign in to leave a comment.