Parent and Child Tickets - Ease of Use

[simon.carter]

We would like to see an improvement on the way parent tickets are created and handled.

It would be hugely beneficial to have some unique identifier when a ticket is made the parent, to allow for easier reporting on the associated linked child tickets.

Essentially a ticket could be marked as the parent > All children tickets linked > Children pick up the attributes of the parent > Resolution details are cascaded to Children and closed.

When reporting it would then only pick up the Parent ticket as a sole issue. 

Please share your thought, views, suggestions etc... 

[simon.carter]

Thanks all for the suggestions, I will look into these to see if they can provide a solution for us. :) 

[Dirk Ronsmans]

@simon.carter ,

Just a thought but wouldn't you be able to get this more specific by creating a specific related issues link?

That way you can filter the report on that link only.

The resolution would need to be an automation tho

[Alex Koxaras _Relational_]

Hi @simon.carter it depends on what exactly is your need:

• Reporting
• Parent-child handling automation
• Both

For reporting, what @Martins Vanags - eazyBI suggested could do the job for you. For handling the tickets, you need to make certain automations to meet these requirements, either by using workflows and apps, or by using Jira Automation.

[Martins Vanags - eazyBI]

Hi @simon.carter 

You could explore the eazyBI app and import linked issues for the parent issue for analysis.

See some use-cases discussed here:

https://community.eazybi.com/search?q=linked%20issues

Martins / eazyBI team