Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

This article explains how to set the scope of a filter in Jira to either Global or Private using Jira Command Line Interface (CLI).

Instructions

The setShareScope action in Jira Command Line Interface, allows the filters to be available to either Global or Private.

  1. Before creating a filter in Jira, set the scope of the filter using the action setShareScope as given in the below example.

    Code Block
    themeMidnight
    --action setShareScope --value Global

    The above action will d efault defaults the filter share scope for the current user to GLOBAL.

  2. Now, create Create a filter using createFilter action as given in the below example.:

    Code Block
    themeMidnight
    --action createFilter --name filterforTSboard --jql "project = TESTER01 ORDER BY Rank ASC"

    The above action creates a filter named "filterforTSboard" for the Jira project "TESTER01".

  3. To verify the filter permissions from Jira UI, log follow the below instructions:
    1. Log in to Jira as an administrator. 
    2. From the top navigation bar, click on Issues
    , from
    1. .
    2. From the dropdown select
    manage filters
    1. Manage filters option, as shown in the screenshot below
    .
    1. :
    Image Removed
    1. Image Added
    2. As the below screenshot indicates, the filter "filterforTSboard" has no restrictions and can be viewed by any logged-in user.
    Image Removed
    1. Image Added
  4. Similarly, the filters can be restricted by setting the scope to "PRIVATE". Refer to the sample action given below for the same.

    Code Block
    themeMidnight
    --action setShareScope --value private


    Code Block
    themeMidnight
    --action createFilter --name filterforTSboard-1 --jql "project = TESTER01 ORDER BY Rank ASC"


  5. The filter "filterforTSboard-1" will be is set as private Private in Jira as shown in the below screenshot.:


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.

...