A way to pull parent info into subtasks for reporting/filtering purposes?

Question

Hi there... What I'm trying to do is view certain info about a subtask and its parent in just one view. Ideally, I'd also be able to filter this view by ticket statuses. My biggest problem with Jira search filtering is that when you choose columns to display, it doesn't seem like you can dynamically be like, "show me this value from the parent ticket," you just pick general ticket fields and it'll display values based on the exact tasks or subtasks returned.

To put it simply, the parent tickets have important date info, but the subtasks tell me who is working on the action items. I'm interested in viewing the work of those subtask owners, but being able to quickly skim through the parent dates while I do, so I can determine who has upcoming action items to complete.

I was thinking of doing the following:

* Dynamically pull parent ticket data into subtasks - maybe using smart values to populate custom subtask fields?
* Creating a simple search filter view, and adding a column for the new custom fields.

Is it even possible to use smart values that way? What else can I do if not...

Ilze Leite-Apine - eazyBI · Answer

Hi @Kate

You can do that also with Jira apps. eazyBI is a Jira app for reporting and charts, and analyzing data by parent/sub-tasks or epics/subtask/parent hierarchies is out of the box there.

You may want to check out the eazyBI demo report that demonstrates this ability: Issue Epics Gantt chart.

In this report, if you open Table view and add issue properties (from "Measures") "Issue type" and "Issue assignee" in the table, as well as apply cell formatting to highlight sub-task rows or other important information, you would get a report similar to the below:

Quantitative values (like "Hours spent") show totals on epic and parent levels, and they include data from their lower-level issues. Issue attributes or properties (as type, status, assignee) are shown for each issue. You may expand or collapse rows to see only particular level issues or the project level for totals.

Contact our support team support@eazybi.com if you have any questions!

Best,

Ilze, eazyBI Customer Support consultant

Bill Sheboy · Answer

Hi @Kate

Yes, you may use smart values that way, and...

How you try to solve your use case depends on how often you need to do this and what actions you plan to take with the information.

* Need this often, and inside of Jira to decide actions/updates* You could do what you describe with custom fields and multiple automation rules to ensure issues are kept in synch
* Look at the built-in dashboard gadgets to see if they can roll up data in ways that might help.  For example, the two-dimensional filter gadget.
* Look at the marketplace for addon apps for both JQL scripting and rollup views of parents/children
* There are community posts of future work to show more information available on the basic roadmaps, so eventually that might solve your need.  No timelines on that info were listed.

* Need this less often and are okay with working outside of Jira* Use either an data export or Atlassian addins for Excel or Google sheets to join the data in a spreadsheet and report how you wish
* Use the REST API to pull data out into another reporting tool

Best regards,
Bill