Has anyone had experience with project issues being set to the default field configuration and then wanted/needed to change to a custom field configuration? We are having issues with this and need to make this transition.
We've dealt with that many times.
We start by duplicating the default field configuration and changing the new FC name to something descriptive. Then we make the changes necessary to the fields that we care about. When that's done, we switch schemes in the project to the new one. Voila!
Hey Trena,
Yes, we have made several of those changes. I always start with a copy of the default, and then make the changes to the copy. I then go ahead and create a new Field Configuration Scheme, link the new FC to the new scheme and the new scheme to the project, replacing the default.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Probably the third most common thing we change in projects! (After workflow and all the other field stuff!)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.