What is The Use Case For Creating an Issuetype as a Subtask in JSW?

[Franklin]

I came across this for the first time in another consultant's project configuration and I'm trying to wrap my head around it. Unsuccessfully. I've been using Jira Server / Data Center for 10 years, but I'm relatively new to JSW. What's the use case for creating an issuetype as a SUBTASK rather than just create a child issue subtask? I don't understand the purpose. 

The reason I ask is because it threw off my automation run. I was branching on subtasks when the issue itself WAS a subtask, but it was also an issue type. Confusion ensued. I finally treated it like an ordinary issuetype in my JQL expression and the automation ran. Still though...

[Trudy Claspill · Accepted solution]

Hello @Franklin 

This appears to be essentially a duplicate of your other post.

https://community.atlassian.com/t5/Jira-Cloud-Admins-questions/What-is-The-Use-Case-For-Creating-an-Issue-Type-as-a-Subtask-in/qaq-p/2498115

...which has already received responses.

If you want to dig into what was happening with your automation rule, we would need information about the rule itself and more information about the issues involved when the rule executed.

[Franklin]

Thanks Trudy. I was more interested in the use case/business case. Why was this functionality introduced in JSW? I don't see the use case.