In my Jira Structure, how do I show tasks not created by me under my epics

[BmOrchard]

I'm trying to build a Structure to show my Epics (the ones I am creator/reporter/assignee) and all the "Issues in Epic" whether I am the creator/reporter/assignee or not.

I also want the Structure to show tasks (not part of an Epic) assigned to me (like in the "No epic" section).

This org uses multiple Jira projects and we have thousands of Jira issues, and I need to just filter down to the ones I care about.

Below is what I have for "Insert Issues".  It's worked great so far, but when a co-worker creates a task and assigns it to one of my Epics, I can't see it in the Structure.  But, when I remove the "myname" conditionals, it shows way to much.  (BTW:  we don't use Stories.)

project in (myproject, thebossproject) and (reporter = myname or assignee = myname or creator = myname) and status != Done

Any help would be great!

[Stepan Kholodov _Tempo_ · Accepted solution]

Hello @BmOrchard 

There might be a contradiction between your requirements and the configured setup of your structure. Your structure is built the following way:

1. First, all issues that are assigned/reported by you are added.
2. Then, they are grouped by Epic, so issues are either then placed under their parent Epic, or they are placed in the 'No epic' folder. This includes Epics themselves - since they don't have the Epic Link field, they end up in the 'No epic' folder, too.

If your goal is to see:
a. Epics and orphaned issues that are reported/assigned by/to you;
b. all issues of these Epics that are reported/assigned to/by any other user,

then you can rework the Inserter's condition to something like this:

(assignee = you OR reporter = you OR creator = you) and "Epic Link" is empty and project in (...) and status != done

As a result, you should get the list of all issues that match the 'a' condition.

Then, add the Extend Issues Under Epics Generator for adding all issues from the condition 'b'. No need to use any groupers or filters in this scenario.

If any user creates a news issue in one of your Epics, the issue should appear under the Epic right away.

And a small detail - if you're using the Sort by Rank generator, there is no need to add the ORDER BY Rank in the JQL query; the sorting is done by the generator.

I hope this helps. If you need further assistance here, or if you have other questions about Structure, please reach out to us directly at our support portal.

Best regards,
Stepan
Tempo (the Structure app vendor)

[BmOrchard]

@Stepan Kholodov _Tempo_ Thanks for the help.  Your suggestions mostly worked, but this is what I did.

• Insert issues:  project in (myprojects) and (reporter = me or assignee = me or creator = me ) and status != Done
• Add sub-tasks
• Remove Inserted/Extender Duplicates
• Sort by Rank

Then to add issues, the "Extend" was helpful -- but not helpful.  The choice "Stories under Epics" is not clear.  Our org doesn't use Stories so I didn't think that would help.  However, by choosing this, it actually extends to other tasktypes.  

But ... even though I have "status != Done" in the above Insert, the Extend function actually pulled in all the "Done" tasks.  So I added:

• Filter issues: status != Done

And that did it!  The other benefit, previously I had "Group by Epic".  This would show the Epics with the tasks under them, and then the Epics listed again under the "No Epic" folder.  Now I have "Sort by Epic Name" (after the Sort by Rank) and now the No Epic folder is gone and my personal tasks (not under any Epic) are together at the bottom of the list.

So, to summarize, under the Structure name I have the following (ordered like this):

• Add issues belonging to epics
• Add sub-tasks
• Remove Inserter/Extender Duplicates
• Filter issues: status != Done
• Sort by Rank
• Sort by Epic Name
• Insert issues: project in (myprojects) and (reporter = me or assignee = me or creator = me ) and status != Done

There might still be some redundancies or unnecessary things here -- and I'll play around with it some more -- but this is working for me.

[Aaron Williams]

Hey @BmOrchard 

Do you have a screenshot of the "structure" so I can see what it is you mean? 

This may help troubleshoot the issue. 

Thanks

Aaron. 

[BmOrchard]