top of page

HowTo (Cloud version)

Installation

This is done through the Jira Apps section. Search for "Issue Type Filters" and install. If you cannot find it, please contact us.

​​

Thereafter the menu item is found in the Apps menu. The Configure link (Apps admin section) will take you there as well.

​​

Only Jira Admins can see it.

Setup (With example)

1. Click the App (top header menu), and click Issue Type Filters (under Your Apps).


2. click "Create scheme"


3. Choose a name and save.

​​

4. Click "rules", to set up the rules of the scheme.

​

A rule is a definition of an issue type, and who can create it. "Allow all" means everybody can create it (logged in users). Groups/roles can be selected as an alternative to "allow all". 

​

An issue type can be hidden totally by deselecting "Allow all" and not choosing groups/roles.

​

Make sure to define the default rule as well.


5. Save the scheme when done.

​

6. Back in schemes, click "Associate" to associate the scheme to projects. You can decide to associate multiple projects.

​

7. Check that it works now, by opening the "Create Issue" dialog, and choose a project you associated the scheme to.

​

8. Now feel free to add other schemes/rules as you see fit.

​​​

Effect

When the filter has been added, observe the effect: Create a JIRA issue. The Issue Type input box would appear like this, if only Task and New Feature was allowed.

​

​

​

​

​

​

​

​

​

​

​

​

​

​

​

​

​

​

​

​

​

​

​

​

ug_6.png
Limitations

Developing for Jira Cloud is more limited than DC/Server. So there are limitations:

​​

1. Due to the Jira Cloud UI API (aka Forge), all issue types cannot be hidden in the Create Issue dialog, contrary to the Server/DC edition, where anything is possible.

​

So make sure that:

  • At least one issue type is ALLOWED for all. And, 

  • that (or those) issue types are in the associated projects of the scheme.

​​

2. The security part (available in the Server/DC edition) is not supported.

​​

3. "Roles membership" checking can be a bit slow. We are working on making it more efficient.

​​

4. Only team managed and company managed projects for Jira Software and Jira Work Management are supported.

​​

5. Subtask's filtering (subtask create) is not supported. 

​

Server/DC to Cloud migration

The DC version of the plugin (from 5.4.1.0) now has the option export the schemes and rules to a JSON file which can be imported into the Cloud version.

​

To migrate:

​

  1. Click to get to "Issue Type Filters" (Manage Apps section) on your Server/DC instance.

  2. In the bottom, there's a link to export. Download that file and save it. Open it in a raw text editor.
     

  3. On your Cloud instance, go to "Issue Type Filters" in Apps menu.

  4. In the top right under Documentation, click "Server-toCloud migration". A window opens.

  5. Copy the JSON contents from the opened editor (step 2) into the text area.

  6. Click "Prepare: .."

  7. Review warnings.

  8. If satisfied, click "Import..", wait, and reload page to review the schemes.

​

Notes:

  • For best import, names must match: project names, issue types, group names and roles names.

  • If the migration tool cannot match a name, the "entity" is skipped, e.g. an association to a project will not happen if the project is not found with the name.

  • The migration window (after Prepare: ..) will warn about these things.

  • Email us at yp@youngplugins.com if something seems to not work correctly.

​

bottom of page