This article shows explains how to set the scope of the filters created a filter in Jira to either Global \Privateor Private using Jira Command Line Interface (CLI).
Instructions
The setShareScope action in Jira
...
CLI, allows the filters to be available
...
either globally or privately with Global
...
and Private settings respectively.
Before creating a filter in Jira, set the scope of the filter using the action setShareScope as given in the example below example.:
Code Block theme Midnight --action setShareScope --value Global
The above action will default This action defaults the filter share scope for the current user to GLOBALGlobal.
Now, create Create a filter using the createFilter action as given in the example below example.:
Code Block theme Midnight --action createFilter --name filterforTSboard --jql "project = TESTER01 ORDER BY Rank ASC"
The above This action creates a filter named "filterforTSboard" for the Jira project "TESTER01".
- To verify Verify the filter permissions from Jira UI , log in to with the instructions below:
- Log into Jira as an administrator.
- From the top navigation bar,
- click Issues.
- From the dropdown select
- the Manage filters option, as shown in the screenshot below
- :
As the screenshot below
- indicates, the filter "filterforTSboard" has no restrictions and can be viewed by any logged-in user.
Similarly, the filters can be restricted by setting the scope to "PRIVATE" Private. Refer to the sample action given below for the same.:
Code Block theme Midnight --action setShareScope --value private
Code Block theme Midnight --action createFilter --name filterforTSboard-1 --jql "project = TESTER01 ORDER BY Rank ASC"
- The filter "filterforTSboard-1" will be is set as private Private in Jira as shown in the below screenshot.
...
- screenshot below:
Info |
---|
Please note that the scope of the filter can only be applied during filter creation but not while updating. Hence setShareScope doesn't set the filter scope when performing updateFilter CLI action. |
Info |
---|
It is recommended to test this scenario in a non-production environment, or run the action with the --simulate parameter to verify the behavior before deploying. |