Project Categorization

[John Churchill]

Is there any way our team can keep our projects somewhat separate but still allow access. In our environment, we have a large-ish group whose constituents all work with data but the team has started treating their individual programs as projects which doesn't seem correct. These would be projects that never end 🤔. I think what we really want is to have some way of keeping our projects separate from other programs. The idea isn't to limit access to them but is there a grouping above the level of a "Project" that can be used to group projects together in a hierarchy.

Programs are like "Data Management", "Data Practices", "Data Governance", "Data Operations" and each have their own projects. Is there any way for us to work within a hierarchy above the level of "Project".

[John Funk · Accepted solution]

Hi John,

Why don't you just do that with the Project Category field? 

Here's an article if you need more information (of maybe you have already thought about that and dismissed it).

https://community.atlassian.com/t5/Jira-articles/What-Good-are-Jira-Project-Categories/ba-p/2860343

[John Churchill]

I'll have a look at that. Thanks!