Unable to configure Custom Sub-Task Issue type to meet our workflow needs

Question

When we create a Subtask issue type (child ticket), Jira automatically configures it to validate with the Parent Ticket. For instance, when I select to 'Complete a Sprint' and there is a Parent Issue Type listed at Sprint done, but there are one or more Subtask issue types (child tickets) that are not 'done', then Jira throws an error saying that all subtasks need to be done before the parent ticket is marked as done. Is there a way to create a Custom 'Sub-task' Issue type that DOES NOT follow this child to parent validation? We would like to add 'Automation' Subtasks underneath our Stories that may need to be completed one or two Sprints after the Story is Sprint done (but before it is released into Production). Can someone help with this?

Thanks!

Mark Segall · Answer

You should still be able to report on linked issues similarly to how you report subtasks with some adjustments.  Can you share what JQL you're using right now?

Wais Mojaddidi · Answer

Thanks Mark.  This is helpful and confirms what I expected.

Regarding your example of linking the Automation Testing issue types to the Story:

* I like the idea of automating the linkage with the parent ticket (even though its not really a parent ticket).
* We still need the ability track and report on the the pass and fail of the Automated Testing issue type.  Is there a good way to do that in this example? Right now, our Manual Test Sub-Tasks have an automatic child to parent linkage to the Story so the reporting is easy.

Mark Segall · Answer

Hi @Wais Mojaddidi and welcome to the community!

Yes sub-tasks are intended to be tied to their parent issues by design.

For your use case, you'll want to look into linking issues instead. This allows issues to be related, but distinct at the same time.  For automation, you would create a new issue with and add link type to your creation step to ensure is has the link to the "parent" ticket.

Note - Linking issues will not behave the same way where you see them tied to each other on the board, but you will be able to perform queries and other logic to keep things tied together.