Filters are a very useful Jira feature : they allow you to execute park searches without having to recreate the same research over and over. Filters are visible in the exploiter interface and are normally used to display certain data in Dashboard gadgets, Project Boards, and Project Reports. You can besides use filters to create drug user notifications and keep them updated about issues matching a percolate research .

Creating Filters in Jira

In order to create a trickle, go to Issues > Search for Issues  to define your research. Make certain to execute it to confirm that the syntax is correct. ultimately, pawl Save as  and choose a name for your new filter. That ’ s all there is to it !

You can besides create lists for your darling filters. To add a filter to your favorites, precisely pawl on the star picture next to the percolate name .
To view the trickle you merely created, click on Issues .
If you besides use Confluence and have it connected to your Jira, you can display search results on a Confluence page by copy-pasting the filter URL to the page. Confluence will mechanically add the Jira issues macro .

Configuring filters in Jira

To access your filters, voyage to Issues > Manage Filters. From there, you can edit your trickle ’ sulfur details adenine well as work on filters that other users have shared with you .
Users can besides Manage Viewers and Editors and Manage Subscriptions for their filters .

How to manage Viewers and Editors

By default, a percolate is set to Private, which means only the user who created the trickle can see it. In order to make it visible to other users, you have to parcel it with them. Viewers and Editors can be set to Public, Groups, Projects ( including specific Project Roles ), or any logged-in drug user .
Users with View permission can see the filter, use the filter in Dashboards, Project Boards etc. and see the filter ’ second question search. Users without View license will not be able to do any of the above. They besides won ’ metric ton be able to see any Dashboard gadgets based on those filters .
Users with Edit access to a filter will have all the permissions viewers have, plus the ability to edit the filter by changing the question. They can besides edit filter details like its name and description, and edit the filter ’ mho view and edit permissions by adding or removing users .

Filters used in Project Boards are shared with all users who have access to that Board. If you create a Project Board based on a save Private filter and partake the Board, the filter will besides change from Private to Shared .

How to manage subscriptions

exit Filter e-mail subscriptions are used to keep users informed about updates to the filter. Set a question, define a run clock interval, and Jira will send emails with search resultant role snippets at each time interval. To access your subscriptions, voyage to Issues > Manage Filters > Subscriptions .
Both the filter owner and any users who can see the trickle will be able to add subscriptions. You can besides define different subscriptions and run time intervals per group. Subscriptions are not just a bang-up way to stay informed about fresh incoming issues ; they besides allow you to keep track of high-stakes issues for your clientele. Be mindful that the subscription electronic mail will only include the first 200 search results, though .

Every filter has one owner. By default, this will be the drug user who created the filter. merely the owner can change percolate possession or delete the trickle all in all. Filter ownership can only be changed for share filters, and entirely by the Jira administrator ( tied though they are not the owner ). To configure ownership, go to the top right corner  > System > Shared Filters. Use the cog adjacent to each trickle to change the owner .

Best practices for using issue filters

Beware of the change

Filters are application-level items. That means changing a filter will change the results of the search for every element using that lapp percolate. Make surely to check for shared users and subscriptions to that percolate before making any changes, so you know who will be affected by it .

Write efficient JQL queries

Creating queries for filters can be crafty : Jira provides many unlike ways to filter to get like results. Filters should always be based on projects, so they focus on information relevant to you. It can be utilitarian to start with a more general research ( e.g. by Project or Status ) and then narrow your scope to the specific information you need ( e.g Priority, fields values ). It ’ second besides highly recommended to create queries that will require minimal update. Be coherent in the direction you create searches, so they will be easier to understand. The basic concepts behind creating JQL queries are listed here. If you want to try something more complex, try the functions provided here .

Keep it consistent

similarly, you will need to be consistent when naming filters. Since all users can create and share their filters, your Jira case may be dealing with a great many issue of filters. If there is no naming convention, it will finally be difficult to find the filter you ’ ra looking for. There ’ sulfur besides a major gamble of duplicate trickle names. That ’ sulfur why it ’ south highly recommended to define a naming convention for all users to follow .
Be certain to check share filters for any users whose access needs to be deactivated ( e.g. when they ’ rhenium leaving the company ) and their percolate ownership transferred to an active user. The most efficient way would be to have one designated exploiter wangle and editing these.

Need help managing your filters ? Contact our support team or get in touch with your local anesthetic sales executive .

beginning : https://coinselected
Category : coin 4u

Leave a Reply

Your email address will not be published.