Move Custom Fields between Spaces, Folders, and Lists | Voters

Move Custom Fields between Spaces, Folders, and Lists

complete

Nate

It would be very useful to be able to take a Custom Field (that I brought over from 1.0) and move it onto a List or a Space instead.

June 20, 2019

Caroline Ginty

marked this post as

complete

Pinned

Hi everyone! I am excited to share that this is available as part of the Custom Field Manager in ClickUp 3.0. I'm closing out this request, but please feel free to create new feature requests with any additional functionality you'd like to see in future versions. Thanks!

pixojoy

Please visit this new post. I wrote about us requesting the removal of the paywall on the Custom Fields Manager. Please share your experiences in the comments and share this post with your teams. https://clickup.canny.io/feature-requests/p/remove-paywall-for-moving-custom-fields-down-the-hierarchy-or-warning-prompts-ac
Darius Family  
David Sanchez
Пономарь Алексей
James Wooldridge (idk which one, there's 2 of you)
Ricardo Brandão
urisobi
Alexia
Becky Hile
Gian Luca D'Intino-Conte
Thomas Subias
Eugen Lehm
Tami Liss
John JM
Tagging everyone who had either commented or liked recent comments about the paywall concerns

James Wooldridge

pixojoy: I find it hard to use the term "feature" here. This is more of an admin function. It would be on par with saying you can add users but can't delete them until you upgrade :)

James Wooldridge

pixojoy: Nope sorry, no warning. It took me a while to figure out what was going on and why the field has appeared where I didn't expect it.

I have logged bug ticket for it.

James Wooldridge

pixojoy: It appears to be a paid feature at the Everything level :(
And a word of caution, if you copy a View that contains custom fields from a lower level up to Everything, the custom filed will be converted to be Workspace wide, and no you can't undo it. Caroline Ginty
I have recently spent many hours creating replacement fields at the level I want and moving data across to "undo" this.

Caroline Ginty

marked this post as

complete

Ricardo Brandão

Caroline Ginty: is it available in all plans?

Michael

Caroline Ginty: oh yeah.. this one too! 🦾

Пономарь Алексей

Ricardo Brandão: as I see now, it’s available on expensive Business plus only.

Ricardo Brandão

Пономарь Алексей: Bummer!

urisobi

Caroline Ginty: what, business plan only??? I already on payed membership. And making future like this necessary for all.

Alexia

Caroline Ginty: Is this true? This can only be marked as COMPLETE for Business Plus, not all plans?

pixojoy

Caroline Ginty Ricardo Brandão Пономарь Алексей urisobi Alexia posting this here too. I made a post a while back to counter this too if you can direct your people there for an upvote https://feedback.clickup.com/feature-requests/p/remove-paywall-for-moving-custom-fields-down-the-hierarchy-warning-prompts-activ

pixojoy

Is this feature truly being paywalled? When editing a Custom Field in 3.0's Custom Field Manager, I get prompted with this notice after clicking, "Change Location."

I'm already on the Standard Business plan..

Darius Family

pixojoy: It would appear so :( Frustrating because CU is so awesome, but when we all start our CU journey we don't necessarily setup our workspaces in the most optimal manner. Over time, we work out better ways of arranging spaces and the inability to move the without upgrading to access the Custom Field Manager. I hope the CU team might reconsider this...

pixojoy

Darius Family: I hope so too. Users new to Clickup are most in need of this feature, in my opinion.

I think that there's little introductory guidance for a proper "structure" inside of Clickup itself. Having this corrective-feature behind a paywall feels like a punishment for having explored deep inside the software.

David Sanchez

pixojoy: I agree, this is adding insult to injury. It's at best a half-baked feature so far. Even working perfectly, it should be available in all paid plans.

Пономарь Алексей

pixojoy: that’s really unpleasant :(

pixojoy

Пономарь Алексей: David Sanchez Agreed..

pixojoy

They must add warning prompts for this at the very least. It's too easy to make this big of a mistake without realizing it during the process of restructuring Spaces.

pixojoy

Oof, yeah they need to embed warning prompts into the UI for stuff like that if this correction feature is to remain on higher-tier plans. Otherwise it feels like "betrayal" having to pay more than we already are, for a lack of a better word.

pixojoy

I agree, it's a necessity

Natalie Williams

this analogy is so on point! I've lost so much time this year because fields can't be dropped down the hierarchy, it's getting to the point now where I'm analyzing how much time each week I'm losing to things like this so I can decide if I'm staying or going.

pixojoy

Natalie Williams There are some bugs too that are converting custom fields from list to workspace. It's happened to me 4 times since I had posted this. 
The week's amount of time it takes to convert them all back became too much work to keep up with when it kept converting back under my nose. Just because of some bug. 
I've given up on this feature being on the standard plan, and therefore my workspace is a mess. I can't trust my data to be handled properly on the standard plan, and it's not fun anymore. I'm just using a task with messy checklists at this point.

pixojoy

Natalie Williams I made a post a while back to counter this too if you can direct your people there for an upvote https://feedback.clickup.com/feature-requests/p/remove-paywall-for-moving-custom-fields-down-the-hierarchy-warning-prompts-activ

Natalie Williams

pixojoy I haven't noticed any CFs being converted, but I also haven't been watching for that. I'll be paying attention to what CFs are on the tasks as I work this week though.

I've got some messes in my space as well. I've contemplated moving more since the roll out of 3.0, the space that's wasted, the annoyance of having to navigate to 3 tabs to see dependencies and linked tasks, the downgrading of the gantt views, the CF issues, the remap subtask bug, the change in options and then moving of the multi-select action bar...it's getting more and more inefficient. My hangup on moving is the time it will take to move, which as more time winds up being wasted is becoming less of a deterrenet to leaving.

Ryan VanGundy

I bet a lot of folks have found their way here because they're in the same situation we're in. We accidentally created some custom fields at the global Workspace level, used them everywhere, and then realized that this was the wrong move. It's really hard to move things out of the Workspace level in to the lower-level hierarchies, you have to delete the custom field and recreate it. And there's no great way to bulk migrate the values from the old custom field to the new one across all your tasks.
For most of us, I bet we don't care that much about the custom field manager. We just want to move some custom fields out of the Workspace view, and then we're back on track. I'm asking support if they will just run the query on the backend to fix this for us. 🤞
(Edit: they won't do it)

sia nami

Ryan VanGundy: 
i have same issue
did you find any easy solution without recreating custom fields?

Ryan VanGundy

sia nami: ClickUp 3.0 and the Custom Fields Manager

Gaurav Jain

Ashley Waters

I really hope that this feature is next up in the roadmap to be released because I need it ASAP!

Devon Moran

Merged in a post:

Allow adding existing custom fields to the space-level

Michael J. Stallinger

I've already defined custom fields on the project(folder)-level. Now, I'd like to make them generally available within my space. How can I achieve this?

Thanks!

May 4, 2023

→