Any suggestions for mimicking "sub-components" on tickets?

[Trina Silverglate]

Hello - I am looking for a solution to a problem identified back in 2021 here: 

Solved: How can I categorize issues by type?

I would prefer something that does not require the tickets to have multiple components assigned, but rather would allow me to display the Jira tickets in a hierarchy view.

I do NOT want to use issuetypes, because there is literally no information to put into the issues and they just create clutter and become empty folders.

Example:

Let's say that I created components (e.g. "MySQL", "Config", "App Sec") which can be assigned to tickets.

In addition, I want to be able to align tickets with sub-categories /sub-components (e.g. MySQL: Schema Mgmt, Data Archival, Config: Secrets Mgmt)

Any suggestions?

[emre]

Hello,
We’d like to suggest an alternative solution for the feature you’re looking for. With our application, Configuration Management Toolkit Cloud, you can build a hierarchy by creating subcomponents and assigning them to work items. Using our custom JQL function, you can query a parent folder or component and retrieve all related child work items that are connected through its subcomponents.

Assign components to issues using our Subcomponent Version Picker. For example, you might have an issue summary that reflects a specific component assignment.

  
Our custom JQL function subcomponentsOf helps you retrieve all related child issues by taking two parameters: the project key or name, and a parent folder or component (e.g., the Compressor folder). This function recursively gathers all child components and their descendants, returning any issues linked to them. It supports both folders and components, as well as deeply nested structures.

Additionally, you can easily visualize the full hierarchy of assigned components or versions on the issue view. 

Disclaimer: I work for the vendor who developed this application.

[Kim Euker]

Are you on JSM Premium?  If so, why not use an asset field(s) to do the subcomponents.  Per the Issue Scope AQL here, Components is one of the out of box fields that can be used to filter your assets.

[Trina Silverglate]

This is for Jira Cloud... is JSM, Service Manager?

[Kim Euker]

Yes, so long as you have the Assets module, you can accomplish my suggestion using Assets, no matter if the application is on Jira Software or Jira Service Management.  

[Aron Gombas _Midori_]

I think Jira Service Management assets would be the best option, but there is a naive workaround you could eventually use if you don't want to complicate the solution.

You can continue using the built-in non-hierarchical components with a simple naming trick. You combine the component and the sub-component using a separator like "/" to the component name. And then the name simulates hierarchy.

I mean, you just create components named like:

1. "MySQL / Schema Mgmt"
2. "MySQL / Data Archival"
3. "MySQL / ..."
4. "Config / Secret Mgmt"
5. "Config / ..."