Issue summary as Y axis for report per two fields

Hi, I want to create a report that gives an overview about the status of the subtasks for a given parent task. The parent task should be shown as Y axis, the state as X axis and the issue count of the subtasks as totals. To be able to identify the parent tasks by their name, I want to use the issue summary as Y axis, however I can't find that information in the drop down menue. Is there any way to show the issue summary as Y axis?

Official comment

Hello, thank you for your message. Do you want to have several parent tasks with their respective subtasks on the same report? Or would you rather have several reports, each one for a single parent task and its subtasks?

I'd like to have one report that gives an overview on all unresolved parent tasks. The parent tasks should represent the Y axis and the number of tickets should be defined by the number of their respective subtasks. It should lool like this:


So my request has more or less 2 issues: How to show the the issue summary on the Y axis instead of an individual field (like the order number) and how to filter out those parent tasks, that are already resolved.


Hello Holger, sorry for the delayed response.

> How to show the the issue summary on the Y axis instead of an individual field

Unfortunately, it's not possible to use the issue summary for the Y axis. What I can suggest is to create a separate custom field (for example, you can call it "Parent summary") and put the summary of the parent task into this field using a custom workflow.

> how to filter out those parent tasks, that are already resolved

If you decide to take the approach with the custom workflow that I've suggested, there are two options I can think of:

a) You can create a separate value for the "Parent summary" custom field that would mark resolved parents (for example, "Parent resolved"). Then tweak your workflow so that it checks children when a parent issue is resolved, and put the "Parent resolved" value into the "Parent summary" field. After that, you'll be able to filter out the children of resolved parents in the report settings ("Issue filter": `Parent summary: -{Parent resolved}`).

b) You can create a second custom field that would show if the parent is resolved (for example, "Parent state"). Fill in values of this field with a custom workflow when a parent gets resolved/unresolved (for example, add values like "Resolved"/"Open"). After that, you'll be able to filter out the children of resolved parents in the report settings ("Issue filter": `Parent state: -Resolved`).


I hope I got your use case right. Let me know if I can help with anything else, I'll be happy to.


Thanks Liubov,

the workaround is not as elegant as I hoped it would be, but it works!

I created an additional field and a corresponding worklfow for the parent summary and also use it tho show and filter the resolved state of the parent issue as you suggested in option a).


I'm glad it works, thank you for the update! Feel free to ask if you need help with any further questions, we'll be happy to help.


I have to take back my previous assumption that the workaround works. It does not. The usage of the two additional individual fields caused other issues, so I had to remove them and the respective workflows that were based on their information.

This means I need another solution. Why is it not possible to use such an important information as the issue summary as a standard field for reports or worklfows? Why is there no closer connection between parent issues and their subtasks? With the current setup it's very hard to get a good overview of all our tasks.



I'm Sergey from the Youtrack team.

I'm sorry that the current report functionality doesn't meet your requirements. Unfortunately, I don't have anything new to add to Liubov's suggestion other than that you might consider exporting the issue data via REST API and build such reports in some third-party service that is more suitable for your needs. 

Also, please feel free to share the issues you faced with custom fields and/or workflows that prevent you from using Liubov's workaround. We'll be glad to help. 

P.S. if you'd like to get in touch with our support team directly for a quick answer to your question, please fill in a direct request at We'll be happy to help.




Can you please tell me, how to update the ancillary field "parent summary" in the subtask when the summary of an issue of a specific issue type is changed?

I tried several workflow variations, none of them worked. I either get an error message when I try to change the summary, or I can change the summary, but the change is not forwarded to the subtasks. In this case I also get error messages when I want to change the status of a subtask or change the summary of a subtask as subtasks can again have their own subtasks.



A workflow is a way to go here. To help sort that out, please share the following details: an example of your workflow, the error you get, a screenshot of the field's settings. And since this thread is about a different request, please share these details with us directly at Thanks. 


Please sign in to leave a comment.