Too many Jira Projects!

[Joe Mallon]

We have dozens of projects - our products have many pieces. Each project will have at least a dozen components, so we can't push the multiplicity down to that level.

Our support staff will be filing bugs, so they will need to have access to all projects. Is there a way on the Create Issue screen to filter projects so the initial list is not so large? We thought categories would help with this, but categories are not part of the Create Issue screen.

[Joe Mallon · Accepted solution]

We decided to preface each project name with a key and use the type-ahead aspect of the Project field.

[Steve Thornhill]

Sounds like a good way to do it

[Steve Thornhill]

What about defining a naming convention for each project, so the starting 3 letters would give a grouping to each set of projects.

A filter could then be used to show subsets of the total projects.

[Joe Mallon]

How do you employ a filter on the Create Issue screen?

[Tibor Hegyi _META-INF_]

Hi Joe,

The support staff needs to access all projects to create issue in. How would the initial project list would work? What if a project not in the initial list is needed?

If the case is that despite the dozens of project, they will create the majority of issue in a few, you may be able to set up shortcut links.

- either read this to fully create issues: https://confluence.atlassian.com/display/JIRA/Creating+Issues+via+direct+HTML+links

- or save links like JIRA_BASE_URL/secure/CreateIssue.jspa?pid=<id not the key of the project>&issuetype=<id of the issue type>. These links will open the create issue screen with project and type preset.

You can save these links in your browser shortcut bar.

Tibor

[Joe Mallon]

The support staff would know which category the issue was in. What I'd like is to have categories be available in the Create Issue screen as an initial filter on projects:

https://jira.atlassian.com/browse/JRA-6136