Categorising Projects in the JIRA Project Picker

We have around 250 projects in JIRA, and the list of projects was becoming unmanageable when creating an issue, and in the issue navigator. I modified the templates so it groups them in to “my” projects, versus “other” projects:


By default we create projects with jira-users in the Users role, giving people Create Issue and Browse permission in the project. We do this firstly in the spirit of openness, and secondly to reduce the effort for project administrators… if we didn’t do this they’d need to manually add people in to the role when they wanted someone to look at or create an issue.

But the consequence was very long lists of projects by virtue of everyone being in jira-users. “My Projects” are any projects where the current user has an explicit role membership for by name, and any projects where they are in a group that is in a role, which is not jira-users or jira-administrators.

This is not a proper plugin, but feel free to download the source here. (Written and tested against 3.12.2).

2 comments to Categorising Projects in the JIRA Project Picker

  • Very nice for scaling big instances of JIRA. Atlassian should add something like this to 4.x IMO.

    Any chance you could add a README indicating which files, if any, are new or even some diffs against the original source?


  • Hi, I’ve added a readme file, containing the following:

    Please see

    This source jar consists of two modified templates, project-edit.vm and context-searcher-edit.vm.
    They have been modified to display the projects in two optgroups, “My Projects” and “Other Projects”.

    There are two modified classes, and They have a couple of extra velocity helper methods.

    The work is done by a new class

    You should merge in these changes with your jira source… the locations of the classes should be obvious by their paths in the jar file.

Leave a Reply