-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow use of Everything space in Config #25
Comments
H again @1activegeek - indeed, the space Id format has changed and the newer format allows dashes. Could you give me a few examples of the Ids you have (you may replace the numbers)? You may also ignore the error message for the time being until I updated the check, this is just a soft validation - simply hit Return to save it. Let me know if it works! |
Interesting, thanks for the heads up. I'll have to see what happens if I try to set it this way. I thought the error was a true error as it didn't seem to pickup my tags or anything when I had it set this way. The two formats I've seen in my spaces are:
|
I'd love to see support for the global "Everything" level as well! |
Leaving issue open, but unsubscribing as I no longer use clickup |
What is the purpose of your feature request?
I am looking to be able to use the Everything space within my main workspace so that I can use all labels and priorities from all my spaces. I've also noticed that I have 2 spaces with
-
characters and even numbers, that do not conform to the standard. Using the validate command, these are failing to work, as is the Everything space. I'd hope being able to use the Everything space, would avoid the issue with the spaces that have-
char, and also allow me to use ALL my spaces vs just a single space.Describe the solution you'd like
I'd love to be able to simply enter my Everything space, which has the same SpaceID as the Workspace which I am within.
Describe alternatives you've considered
Entering only one space, but I lose access to all of my searchable tags/labels I believe.
The text was updated successfully, but these errors were encountered: