Adding my vote here. We use priority to denote what is the current focus. I don't want to use a custom field because the native priority field is included on every task created. A task/project may not be "Urgent" but it is the top priority for the agent. The developer that designed this priority has confused "Urgency" with "Priority". When managing a whole bunch of projects, it's helpful to know if something is a top priority, but not urgent... and vice versa.

custom fields do sort of a lot unexpected behavior, but as mentioned earlier native support for this is way better.

back end they could go from lowest 1 - default with custom name and color to 999. and simply sort by number. shouldnt be that much of a rework to the one already is in place.

Agreed, and would also like to choose the flag colors.

We need this too, our team is missing an extra priority level between Normal and High

Agree this would be super helpful. Because "Urgent" isn't necessarily a priority - it's a measure of how quickly it soon to be done. Priority can only be high, low, medium etc. Something can be "NOT URGENT" but extremely high priority.

Also the ability to select which is default. e.g. it would be good to have the ability to set the default at "normal", as this would allow my to just change the priority of ONE task to lower it below the default, instead of having to increase the priority of all other tasks to get that order right.

There should be no such thing as "No Priority." If a ticket doesn't have any priority, no one will ever work on it, and the idea should remain in someone's Doc for brainstorming. "No Priority" should not be an option to choose when creating tasks.

This flexibility is key to organisations like mine where we already have established processes around work prioritisation we must align to. The type of priority description will depend on the prioritisation method used and whether it is at a high-level (PMO) or task level (operations). For example: Our IT Team and our PMO will use Blocker, Critical, Major, Normal and Minor whereas other areas like Facilities and Fleet Management may use Very High, High, Medium, Low, Very Low...this could be a deal-breaker for us as Monday.com, Asana and Jira all offer this flexibility already...as do many other competitors, I imagine. As a vendor, it should be your goal to develop what customers need and it is not the vendor's role to dictate process or control how customers work.

Click Up does such an AMAZING JOB of moving this software forward on a continuous basis-- there really is no good reason not to be able to customize "Priorities" at an organizational level. The custom wording and colors are not what we use as a company, so unfortunately, this is useless for us. I tried using tags for this purpose, but I would have to go to EVERY workspace to create them.

This article: https://docs.clickup.com/en/articles/1116076-priorities-clickapp#:~:text=Priorities%20in%20ClickUp%20are%20optional,or%20more%20of%20your%20Workspaces. suggests it would be confusing to have personal priorities - I agree and instead suggest custom priorities should be set at the workspace level.