Hello,
I have a Jira project called "PBI". This project contains epics which must go through a workflow designed for this project (related to approving these epics).
These epics have child issues (stories, tasks) in different projects (DENIK, CTP etc.). When I create a plan I would like to see list of these PBI epics with their children.
I have a filter for this plan which says 'project = "PBI" AND issueType = Epic'. I know that to see the child issues related to these epics, I also have to include them in the query. But this seems to be impossible because what would need a subquery which would say "select also tasks or stories which have a parent in project PBI".
I know there are some extensions that would help me to create such a subquery, but that is an extra cost to Jira Premium and even those plugins are not real-time (meaning that when you update some issue, it takes some time to reindex the filter).
Is there another way how to achieve that just using Jira Premium? It should result in this (displaying epic with children from different projects, not only epics), but without external plugins.
Thank, Tomáš
Hi @erathian
Welcome to the community.
You need to changes the plans sources, add the required projects or amend the filter to include the projects where the stories and other issue types reside.
No you don't need a sub query, of course this will probably get more items in then you want.
Then set a differentiator on the child issue, like a component or label.
Simply JQL: Project = xxx and type = Epic or project in (xxx,xxx,xxx) and type in (story,task) and label = zzzz
Otherwise, yes you will need a 3rd party app from the marketplace
Hi Marc,
thanks a lot, I understand. This might be a little difficult because of these projects' history.
Is there any plan for Atlassian to change it?
Maybe we think about that in the wrong way and there Is a better workflow than we use. There is a project with all the epics (PBI) that can be done in our company and these epics have some stages (they go from idea phase to refinement, to approvals, and then they are in progress, deployed, and finally evaluated and closed). They are in the same project because of the workflow and statuses they must go through.
And these epics have multiple children from different projects and teams. So the PBI should be the project with these big things (epics, possible initiatives) where we can also see their current state and be able to see it as a whole with their children (using the timeline in plans).
Tomáš
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @erathian
AS the PBI project is your high level issue repo, and all work relate to complete it is on other Jira projects
Set your plan sources as follows.
Use a filter for the Epics from PBI and add relevant projects where the work is done as sources.
There is no need that a plan needs only a source as a filter.
This will show all relevant work in the plan.
Atlassian will not quickly change JQL options, could be years or never
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.