Whatever you want it to be. Off-the-shelf, JIRA just has those two as valid types of issue and they work the same way. But you can change them to meet your requirements.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Pretty much - all the sub-tasks behave the same, it's up to you to configure them to do clever things :-)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Issue is the generic term for all items in JIRA (Bug, Story, Task, whatever). The only thing special about a subtask is that it must exist in relation to another issue, its parent. It inherits things like the Epic Link from its parent, but otherwise can be configured with its own workflow and screens, like any other issue type.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
So for example, if a template exist for QA certification for AIX, that template will be clone and a sub task will be created for a new release or patch correct?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Possibly. That depends on how you are setting it up and using it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.