Hello,
Very new to Jira and struggling to create a JQL filter that allows me to see epics and its related children tasks plus all standalone tasks/subtasks that are overdue and have a due date within 14 days. Also having priority, reporter and assignee be easily viewable would be ideal when talking through work with my marketing team. If possible, would love some guidance. Trying to turn my hot mess list (using basic) into a comprehensive, organized report to delve into with my team at bi-weekly standups. Thanks!
Hello @Jewell Sutton
You are talking about 3 levels of issues:
- Epics
- standard item types that Children of Epics, and standard item types that are not children of Epics
- sub-tasks
Are you setting due dates at every level, two levels, or just one level? The answer to that is critical to creating the correct JQL.
Example:
If the Epic has a due date that matches your criteria, but some or all of its children do not, would you expect the children to be included in the results? And what if those children had subtasks where some or all of the subtasks don't match the criteria?
The next question is are all these issues in a single project? What type(s) of project(s) are these issues in? You can get Project Type information from the Type column on the projects list page (Projects > More Projects > View All Projects).
The next question is are you using a "board" to view these issues; i.e. a Scrum board or a Kanban board?
And the last question is are you limited to only the native JQL capabilities or have 3rd party apps been added to your instance to extend the JQL capabilities?
Thank you @Trudy Claspill !
3 levels - yes
We do have due dates at every level, or should. I'll doublecheck the due date field was included in all epics for each project. But do for all other work items and sub-tasks and automation.
I would only expect those children/subtasks with due dates matching criteria to show. If parent's due date doesn't meet criteria, I'd still want those children/subtasks that do to still show up under that parent.
The issues are in 5 company-managed software .. each representing a lane on our marketing team (creative, comms, marketing, events, business development).
As for boards - we've a total of 8 boards total for our 5 projects.
Just launched Jira a few weeks ago (buh-bye Asana!!!), and we've no 3rd party apps added (yet).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If you have due dates at all levels and you want only the items where the due date matches the criteria
that are overdue and have a due date within 14 days.
...then the JQL you would want would be:
For overdue items:
project in (comma separated list of the 5 company managed projects) and duedate < startofday()
For items due in the next 14 days:
project in (comma separated list of the 5 company managed projects) and duedate >= startofday() and duedate < startofday(14)
In the Search Work Items screen you can view the results in Columns and specify the fields/Columns to include, so you could include Priority, Reporter, and Assignee.
The Search Work Items screen provides a simple list that you can Order but you cannot Group. The output will not display hierarchically, but each issue that is a child of another (child of an Epic, or subtask that is a child of another issue) can show the issue key and Summary of its parent if you include the Parent field.
That presentation may not be ideal. You should give some thought to what type of presentation would work best. You might want to show the information in an Agile board, or a Plans view, or on a Jira Dashboard.
Side note: being new to Jira you might want to explore the free on-demand training available from the Learning link at the top of the Community pages.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Appreciate your assistance @Trudy Claspill .. I'll test out your JQL suggestions, look into plans and all related supporting content / learnings to be found ... and see which approach works best for us... thanks again.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Jewell Sutton,
For effective stand-ups, I would recommend creating a Jira dashboard with all the necessary gadgets to display things like the task board, sprint summary, burndown/burnup chart, epic progress, other key figures and charts, plus project-specific information like the one you mentioned. Then, hold the stand-ups “in front” of the dashboard (or share it if it is an online stand-up) to indicate the tasks and specific information about them during the meeting.
Jira offers some basic gadgets, but you can complete your list of gadgets by installing apps from Atlassian Marketplace. Here is an example of Scrum dashboard that you can create for your team, by using our Great Gadgets app + some gadgets from Jira: https://community.atlassian.com/forums/App-Central-articles/10-gadgets-for-a-powerful-Scrum-dashboard-in-Jira/ba-p/1683063
Now, for displaying the list of issues that you mentioned, you could try adding the Filter Results gadget of Jira to your dashboard, configured with a filter like the one mentioned by Trudy and see if it helps.
Danut.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.