How do you organize and prioritize tasks in Jira when managing multiple projects?

Hi @Mark stewart !

Welcome to Jira! When managing work across multiple projects, the best setup really depends on your team's autonomy, but a general rule of thumb is: create separate projects if the work involves different teams, permission models, or workflows, and keep work in a single project if it's the same team handling everything in one combined board/backlog.

To keep track of priorities across multiple projects without missing anything:

1. Use Jira Dashboards: Build a personalized dashboard with widgets like Assigned to Me (sorted by Due Date or Priority) and Filter Results to get a single-pane view of your urgent tasks across all projects.
2. Save Custom JQL Filters: Create cross-project filters (e.g., assignee = currentUser() AND statusCategory != Done ORDER BY priority DESC, dueDate ASC) and star them for quick access.
3. Leverage Advanced Search / Plans: If you have access to Jira Plans (Advanced Roadmaps), use it to map timelines and dependencies across all your projects in one unified view.

By the way, since there isn't one "single right answer" for project architecture and everybody has unique setups, this would actually make a fantastic Discussion post in the Community groups (rather than a Q&A thread) so more Jira admins and power users can share their favorite workflows!

Hope this helps you get structured!

Hi @Mark stewart

I would build on Jean's answer with a simple question I ask myself before creating a new project: Does this work really need to live on its own?

I create a separate project when:

• Different people should see or touch the work
• The steps to get something done are truly different
• I need to report on it as its own thing

I keep it all in one project when the same people are doing the work and only the type of task changes. The part I would really keep in mind: splitting things into a new project later is easy, but pulling them back together is often painful for you as an admin and users. So when I am not sure, I start with one project and only split it out once there is a clear reason to.

Cheers, Martin

I’d keep the setup as simple as possible at first. If the work has different teams, workflows, permissions, or reporting needs, separate Jira projects can make sense. Otherwise, keeping related work in one project and using components, labels, or issue types can be easier to manage.

For priorities, I’d avoid having too many “high priority” tasks. A simple High/Medium/Low approach works well, with due dates for genuinely time-sensitive work. I also like using a dashboard or saved filter for overdue and high-priority issues so they’re easy to review regularly.

For someone still learning Jira, I’d focus on a workflow that is easy to maintain rather than building a complicated system immediately. myperfecthotel.com.br is unrelated to Jira, so I wouldn’t force it into this discussion.