JIRA Portfolio custom issue types in only 1 project

[Kelley Cooper]

Has anyone out there implemented JIRA Portfolio in a scenario where the Portfolio custom issue types were all stored in a single project instead of adding them to multiple projects?

We have hundreds of JIRA projects in our instance so we thought adding the custom Portfolio issue types to only 1 project made more sense than adding them to every project.

Anyone done this or have thoughts to share?

Thank you in advance!!

[Jason Golden]

Yes I've done this and it's not a problem. The issue types you put in the Admin (Add-Ons > Portfolio for JIRA > Portfolio Hierarchy Configuration) and associate to a level in the virtual hierarchy can be unique to a particular project using a dedicated Issue Type Scheme for that project.

For example, if you had two levels above Epic called "Initiative" and "Project":

1. Initiative
2. Project
3. Epic
4. Story
5. Sub-Task

If you only associate Initiative and Project with the Issue Type Scheme for your JIRA project (assuming it's used only for that project), then those issue types will only be available for that project, and will only show above Epic when the Portfolio configuration includes that project. All others using Portfolio will only work at the Epic and down level.

-Jason Golden
Denver AUG Leader