Best practice for categorizing software issues compared to non-software issues in a large project?

[Shane Flood]

If you have a Jira project with 50-100 people I am looking for recommendations on how admins have set up Jira projects to identify software related issues compared to non-software related issues. 

[Brant Schroeder]

@Shane Flood Welcome to the Atlassian community 

There are several ways you can organize issues for your team.  If you want to separate software and non-software issue you could use any of the following:

• Create issue types for each
• Create components and apply them to the issues 
• Create labels and apply them to the issues 

[Craig Castle-Mead]

I'd be leaning towards the Issue Type based categorisation for "Software" Vs "Non-Software" issues. What this even means will be dependent on your company/culture, but when creating an Issue, the first key piece of information is the Type - so using clearly defined Issue Types for Software (Bug, Feature Request) Vs Non-Software (Documentation, Rollout - again, depends on what you're making) to me seems to be the clearest path.

CCM