I'm looking to show Epics from Project A that are associated to Stories in Project B on Project B's Project and Board; I do not want to see all Epics from Project A. I do not see an option on the filters to do that. So far, I've used 'Project IN (A, B)' and contains a keyword, but those would not provide the correct filtering I'm looking for. I want to see if there is a dynamic option that pulls the Epic into Project B as soon as a Story is associated with it. Is there a way to do this?
I’m Maurício, a support engineer at Appfire and I’m here to help you.
Unfortunately, using JQL of Jira, you’ll not be able to do it dynamically.
In the app where my team works, JQL Search Extensions for Jira, you can use this query to find Epics that are associated to another project’s Story:
issue in linkedIssuesOfQuery("project = B and type=Story") AND type=Epic and project = A
Please contact our support if you have any other questions about this query.
We’ll be happy to help you!
Best regards,
Maurício
Howdy Mauricio,
Thank you for the insight. We'll review JQL Search Extensions and see if the product is right for us.
Thank you,
Carlin Jones
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
just to put this out there, another option might be to consider one of the more hierarchy-focused apps from the Marketplace. These apps typically have their own ways of figuring out parent/child relationships between issues, and provide more powerful ways of defining and searching through issue hierarchies. I myself work on such an app, in which your use case would be easy to solve - I'll provide more details below.
The advantage here is that you can actually view your issues in their hierarchy, which depending on your exact use case, may make things considerably easier.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Just to expand on the above, here's how this would look in the app that my team and I are working on, JXL for Jira:
JXL is a full-fledged spreadsheet/table view for your issues that allows viewing, inline-editing, sorting, and filtering by all your issue fields, much like you’d do in e.g. Excel or Google Sheets. It also comes with a number of advanced features, including support for (configurable) issue hierarchies. Once a hierarchy is enabled, you can use JXL's search and filter capabilities to narrow your issues down to exactly what you're looking for.
Once you've got your issues, you can work on these issues directly in JXL, trigger various operations in Jira, or export your issues with just one click.
Any questions just let me know,
Best,
Hannes
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Welcome to the Atlassian community!
How are the issues in project B associated to the Epic in Project A? Are the project B issues children of the Project A Epic?
Are you working with Jira Server/Data Center or Jira Cloud? If your Jira URL is similar to the one below then you are working with Jira Cloud.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Howdy Trudy,
Project B are the stories associated with the Epic in Project A through the Epic Link; we are currently working with Jira Server but we are moving to the Cloud in the coming months.
Thank you,
Carlin Jones
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Jones, Carlin A
Welcome to the community!
Yes, it is possible to show Epics from Project A that are associated with Stories in Project B on Project B's board using JQL filters in Jira. You can use the following JQL query:
project = B AND "Epic Link" in (project = A)
This query will filter out all the Epics from Project A that are not linked to any issues in Project B. It will only display the Epics that have at least one Story linked to it in Project B.
To ensure that the Epics from Project A are dynamically pulled into Project B as soon as a Story is associated with it, you will need to make sure that the Epic Link custom field is available in both Project A and Project B.
You can follow these steps to check if the Epic Link field is available in both projects:
Once the Epic Link field is available in both projects, you can link Stories in Project B to Epics in Project A by selecting the appropriate Epic in the "Epic Link" field of the Story.
After linking the Stories to the Epics, you can use the JQL query mentioned above to filter the Epics and display only the relevant Epics on the Project B board.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Howdy, thank you for the welcome and feedback. When I use 'project = B AND "Epic Link" in (project = A' I get an error returned. I've checked to make sure the Epic Link field is available in both projects. It looks like the error comes from "Epic Link" In (project = A); I'm not sure how else to pull the Epic comes from Project A.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It looks like the JQL you provided is not formatted correctly. To search for Epics in Project A that are associated with Stories in Project B, you can use the following JQL:
project = B AND "Epic Link" in issuesInProject("A")
This JQL will search for issues in Project B that have an Epic Link field that is linked to an Epic in Project A.
Make sure that the Epic Link field is available in both projects and that the field name is spelled correctly. Also, make sure that you have the necessary permissions to view issues in both projects.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Native Jira Jql functionality does not support either
- using a filter for the "Epic Link" field criteria when using the = operator
- the issuesInProject function
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Trudy Claspill Thank you!
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.