Skip to main content

Ultimate Guide on How to Use Filters on Jira for New Employees

About Us
Published by jetbi
31 July 2023
40

In this article, we will discuss what Jira is, what mistakes and issues can occur to first-day users, and how to avoid these mistakes by using filters that improve efficiency and task management. 

What is Jira? Jira is an effective task management tool that helps you track progress, project status, and identification of blockers. Jira is a great app for improving efficiency inside the company. Prioritizing option allows you to be up to date with active tasks and project’s due dates.

What are some typical errors that newcomers to Jira might encounter? Let's begin with an onboarding situation. On the first day of work a task is given, to raise a ticket issue on Jira. Once the task is created and assigned to a project manager it can disappear from a creator's scope of vision. It’s a natural process on Jira that requires the task to go through the workflow of approvals. But yet can be tricky for a new employee. After opening a default filter section there won't be a task that you created, because it’s assigned to your project manager that currently approves the task. This error here can lure a task creator’s focus away to another project or simply create a thought that there are no tasks assigned, in other words, “No work yet”. But it’s better to prepare for a task or start working on it while it’s in the stages of approval. Because the deadline, unresolved status, and blocker is coming... This can lead to a project’s failure and your team's and clients' disappointment.

So what can be done to avoid those mistakes? Now that is where Jira filters step in to save you. Let's start our Jira Filters 101 guide by breaking down the filter sections:

  • Projects - You should know what projects you are working on. (Training, Marketing or Development, etc).
  • Issue Types - You can filter standard tasks, sub-tasks, bugs, and many other things. 
  • Status - Extremely crucial filter to understand what is the stage of your task.
  • Users/Groups- In this filter you see who is the assignee of the project. If a task is under someone's review or work you can always add a comment asking what’s the status, how much time they need to finish. 
  • Reporter- A very important filter, when your task is assigned for approval you won't see it in your task list until you open this filter and write your name. 
  • Priority - Manage your tickets by filtering the priority, starting from blockers, criticals, and going down. 
  • Due date- Submit your work on your time! This filter will show your nearest or past deadlines.
  • Resolution- Another good filter that lets you see what work is not done. 

There are a lot more filters but these are must-haves, must know to keep track of your projects, open tasks, unresolved issues, priorities, and deadlines. 

We would highly recommend to all new Jira users save different layouts of filters. Start with ‘All my tasks’ for an overview, then switch to ‘Reporter’ to see how many tasks are currently assigned to your colleagues, and finish with ‘Unresolved’ to view all tasks that need to be done. 

And finally, don't forget to check your notifications on Jira and your email. 

To sum it up it’s crucial thing to remember how to use filters on Jira as it can significantly improve your productivity and visibility into your project’s status. Review and update filters regularly to stay organized, prepared, and focused!


Volodymyr Gryshko
Marketing Analyst
image
Expertise
Question to the expert
image

We have available resources to start working on your project within 5 business days

1 UX Designer

image

1 Admin

image

2 QA engineers

image

1 Consultant

image
Related Articles
All articles
image
Is Salesforce Winning the Public Sector Race?
An analysis of Salesforce's rapid expansion into the U.S. public sector, tracing its path from cautious early government licensing deals in the 2010s through the launch of Government Cloud in 2012, its pivotal role in COVID-19 vaccine rollouts, and its 2025–2026 push into military and intelligence work via Agentforce and Missionforce. The piece covers major 2026 contracts — including a $5.6 billion Army deal, a $1.6 billion VA agreement, and Pentagon Impact Level 5 authorization — alongside real-world case studies like California's REAL ID processing and the UK's NHS back-office operations. It also examines the structural obstacles still facing Salesforce and other vendors in government tech: legacy IT systems decades old, outdated federal procurement rules, budget constraints, and organizational caution around AI adoption, plus the competitive pressure from Palantir, Microsoft, and Oracle in the race for public sector AI spending.
28 August 2026
image
Why Your Salesforce Flows Are Agentforce's Biggest Problem
This article argues that the most underestimated risk in Agentforce deployments isn't data quality — it's the automation layer: years of overlapping Flows, Process Builder processes, Apex triggers, and managed package logic that no one has reviewed end-to-end. It explains why AI agents inherit automation complexity without the tribal knowledge human admins carry, why technical debt only becomes visible after an agent hits it in production, and why a clean demo is no indicator of production readiness. The article closes with a concrete, tool-by-tool inventory approach using Flow Trigger Explorer, Salesforce Optimizer, Setup Audit Trail, Apex Debug Logs, Agent Builder, and Health Check — scoped to the specific processes the agent will actually use rather than the whole org.
23 July 2026
image
How to Wire Multiple Salesforce Projects in One Org Without Breaking Everything
This article maps the real integration patterns that emerge when multiple Salesforce projects — both managed packages and unpackaged code — share a single org. It covers four concrete patterns: attaching custom triggers to package-owned objects, calling global members exposed by managed packages, writing directly into another project's objects, and runtime-guarded reads of package data. It then addresses access control for authenticated and guest users, including the Master-Detail wall and the without sharing elevation pattern. The piece closes with eight concrete risks (compile-time dependencies that block uninstall, upgrade coupling, silent cascade failures, access invisible to admins) and six actionable recommendations for keeping cross-project coupling manageable.
08 July 2026