Updating the Jira alert for scenarios where we need to create subtask (child issues) within existing tasks.

[OlehPalanskyi]

Description

Problem:
I have a needs create a subtask (child issues) under task, bug, story, epic to keep it under one track.

Solution:
I have extend jira capabilities with a new parameter which help to do that.
By default, it’s off.

jira_parent: Specify an existing ticket that will be used as a parent to create a new subtask in it

For example, if you have this issue hierarchy:
Epic
Story, Task, Bug
Subtask

Then:
As a parent issue, an epic can have stories, tasks, and bugs as subtask (child issues).
As a parent issues, task, stories and bugs can have subtasks as subtask (child issues).
A subtask can’t have any subtask (child issues).

Example usage::
jira_server: "https://example.atlassian.net/"
jira_project: "XXX"
jira_assignee: user@example.com
jira_issuetype: "Sub-task"
jira_parent: "XXX-3164"

Checklist

• I have reviewed the contributing guidelines.
• I have included unit tests for my changes or additions.
• I have successfully run make test-docker with my changes.
• I have manually tested all relevant modes of the change in this PR.
• I have updated the documentation.
• I have updated the changelog.

Questions or Comments

[jertel]

Thanks for the submission! I noticed you checked off the box that states you have included unit tests, but I don't see them in this PR. Can you check to see if they didn't get added to the commit? Once the unit test coverage is included, and the changelog is updated, following the style of previous changes, we should be able to get this merged.

[OlehPalanskyi]

@jertel already done!