Setting importance / priority at the project level

I've got several projects across several teams so I've set up a dashboard to see them all in one place. I have a widget for each team that shows the active projects for that team. The problem is that I can't sort the projects within the teams by importance / priority - i.e. where I need to focus my energy - because projects can't have an importance / priority setting. Tasks can, but not projects.

Does anyone have any tricks that could help with this as projects not having an importance / priority setting seems an obvious gap.

Please tell me I'm missing something obvious!

ps: I've contacted support and the best they could suggest was putting numbers of exclamation marks or numbers at the start of a project name

Find more posts tagged with

Comments

Sarah Dungey

Hi James,

We have a couple of custom fields at the project-level:

1. Project Priority (a single-select dropdown of 1-5, with 1 being the highest)

2. Organization Level (a single-select dropdown to indicate whether a project is a team/department priority, a program priority, or an org-wide priority)

The combination of these custom fields allows us to adjust schedules to prioritize the highest priority projects for each level of the org.

Kevin Thalacker

Hi James,

We do something similar as Sarah. We utilize custom fields to help us categorize each project.

Abigail Saunders

We also have a customized field at the project level called "Priority" and have three levels of High, Medium, and Low. We can report and create dashboards utilizing this field.

James Roberts

Thanks all, I'll look into this.

Marissa Lapierre

Would be a great to have the "importance" field like we have in the task.