Orca Security Subtask creation
Gary Spross
Community Leader 
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Within Orca, there are 3 options to generate Jira issue(s) (see screen capture). The one option is "Open one Jira ticket from an existing ticket". This option creates a main issue and then adds each security vulnerability as a subtask on the main ticket.
What I cannot figure out, and Orca doesn't seem to know either, is how is the Subtask issue type that is used configured? Where within Orca is this specified? If a project has multiple subtask issue types available within it, how can I ensure Orca will use "Sub-task" instead of "Technical Sub Task" (for example)?
