JXL - display issues and subtasks

Bevis HUngate February 18, 2024

We assign issues to users, but not their subtasks.  I want to create a view which shows the issues assigned to a particular user, along with their subtasks.  Possible??

Thanks all!  

2 answers

1 vote
Daniel Franz - JXL
Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
February 18, 2024

Hi Bevis,

If I understood correctly, you’d like to capture all issues assigned to a specified user and the child issues of these issues, even though they are not assigned to the user. This is not possible in native JQL without using any third-party extensions such as ScriptRunner, however, luckily JXL for Jira can help anyway. You do not need any other app for this.

1. You need to define a Sheet scope (JQL statement or saved filter) that captures all the issues you need in your sheet. All of them. This is important, as there will be no further queries once the sheet has loaded this set of issues. If necessary, write a JQL query that returns irrelevant/more issues than needed, that’s no problem. You can filter them out later. A simple example would be: assignee = currentUser() OR issuetype = "Subtask"

2. Enable Issue hierarchy or create a Custom issue structure using Hierarchy levels.

3. Now you should have your issues structured in a tidy, indented, collapse-expandible visualisation. Any unneeded issues in your sheet as a result of the sheet scope potentially being too broad can now be filtered out using Level filtering. In your specific case, you’ll want to set the Issues without parents menu to Hide child level issues or Hide bottom level issues.

Hope that helps. Let me know if I can clarify anything.

Daniel (JXL team)

Bevis HUngate February 19, 2024

Thanks Daniel.  We're using JXL and I'm a big fan.  I think I've done as you suggested, but when I filter on User X it shows fine, but if I then change the Assignee of one of the subtasks, that subtask disappears.  And I understand why, but I want to keep it their in the view regardless of who that Assignee is (many will ultimately be assigned to freelancers, but they're the responsibility of User X and they need to appear for them).  Perhaps I've misunderstood your message.

Thanks again,


Daniel Franz - JXL
Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
February 19, 2024

Hi Bevis. Not sure I understood correctly, but if you're using Column filtering on the Assignee column (as opposed to JQL) to filter out User X, this will by default apply to all rows, i.e. hide any issues not assigned to User X. Level-specific search and filtering could help you here to apply the column filtering selectively only to top or parent level/s and ignore the subtasks.

Looking at your use case, another more general idea would be to create a custom people field to track "responsible person" separately from assignee, and add that column also to your table.

Hope that helps.

Bevis HUngate February 20, 2024

Eureka, got it!!  Now found the level-specific search/filtering icon.  Working perfectly.  Thanks very much

0 votes
Ignacio Aredez
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 18, 2024

Unfortunately, JQL doesn't support directly querying subtasks based on their parent's assignee in a single step. You'll need a workaround(manual work and problematic) or a plugin for more complex queries.

Manual Linking: If the number of parent issues is manageable, you could manually note their IDs and use them to query their subtasks.

Dashboard Gadgets: Utilize gadgets that can help you indirectly monitor subtasks related to the user's issues. For example, use a "Filter Results" gadget to display issues from your initial query and add another gadget that requires manual updating based on issue IDs or other identifiable markers.

Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events