When sub-task is created it's creating a new issue as well.

[Tyler Myalls]

When I create a sub-task it automatically creates another issue - how can I prevent this?

I just want the sub-task to show up in it's parent issue, not as an additional separate issue. 

[Christopher Yen]

Hi @Tyler Myalls could you include a screenshot of what you're describing just so we're all on the same page? 

You don't want sub-task to be a standalone issue or when you create a sub-task a separate issue is being created automatically?

[Tyler Myalls]

I'm fairly new to JIRA, so didn't realize that creating a sub-task automatically creates a separate issue and creates a key in numerical sequence. 

If I create an issue (which in my case I named Customer Service Tickets: CST) then it creates a key with it, which I named CST-##. Example: CST-32 (parent issue).

If I then create a subtask of CST-32, JIRA automatically assigns the next available key number, which is really confusing, especially when I have hundreds of issues. If I create CST-32 it could have subtasks CST-104, CST-157, CST-245, depending on when I added the sub-task, which makes zero sense. 

It would be clearer if subtasks were named based off the issue they're tied to. As an example, CST-45 subtasks could be named CST-45.1, CST-45.2 or something similar - an indicator that clearly indicates which parent issue it's associated with. 

I don't think there's anyway to over ride this. 

[Christopher Yen]

Ah I see, yes unfortunately the issue key is just a counter for any issue regardless of issue type in the project. Outside of being a unique identifier I think most Jira users don't pay much attention to the numbers because of what you mentioned. 

There are views and filters where you can see the nested issue relationships but unfortunately the key does not tell you much other than the order that record entered the table. 

[Tyler Myalls]

It's not an automation I created - I checked that. 

[Maria Ciobanu]

I confirm that. I would also want to know how to solve that.