-
Sub-task
-
Resolution: Done
-
None
-
None
Hi everyone,
Customers can query on Next-gen epics using the parent =. If you want to combine Epics from both project types, an example of such a query would be: "Epic Link" = NPC-6 OR parent = NJDP-5
The Parent field can now be selected as a column in the Global Issue Navigator and exported from Jira.
Regards,
Nathan Sturgess
nsturgess@atlassian.com
Product Manager, JIRA Platform
Original request description
WIth the deploy of the epics and linking the issues to the epics at the Next-Gen projects we can't use the JQL to return issues that are associated to an epic as we can do for classic projects.
Steps to reproduce
- Create a next-gen project
- Create an epic
- Associate multiple issues to the epic
- Go to Issue Navigator and try to perform the search by Epic Link referencing the Next-Gen epic
- No results are displayed
Expected results
Return the list of issues that are linked to the referenced Epic
Actual results
Use parent() function to show the child issues of the Epic. Example:
parent = EPIC-123
- duplicates
-
JRACLOUD-91523 Next-gen Epics can't be used in the Issue search with JQL
-
- Closed
-
- is duplicated by
-
-
- Closed
-
-
-
- Closed
-
- is related to
-
-
- Closed
-
-
-
- Closed
-
- relates to
-
- Closed
-
-
- Closed
-
- mentioned in
-
Page Loading...
-
-
-
-
-
-
[JSWCLOUD-17239] As a user, I'd like to be able to use JQL for Epic Link for Next-Gen project epics
| Remote Link | Original: This issue links to "Page (Confluence)" [ 563410 ] |
| Remote Link | New: This issue links to "Page (Confluence)" [ 570409 ] |
| Remote Link | New: This issue links to "Page (Confluence)" [ 563410 ] |
| Remote Link | New: This issue links to "Page (Confluence)" [ 497734 ] |
| Remote Link | New: This issue links to "Page (Confluence)" [ 497569 ] |
| Attachment | New: Screen Shot 2019-12-19 at 8.58.59 am.png [ 382070 ] |
| Comment | [ @nathan Does that mean we are basing the NextGen epic on color? If yes, it will display all epics with that color? ] |
| Description |
Original:
{panel:title=Atlassian Status as of 12 December 2019|borderStyle=solid|borderColor=#3C78B5| titleBGColor=#3C78B5| bgColor=#E7F4FA}
Hi everyone, Customers can query on Next-gen epics using the _{color:#DE350B}parent ={color}_. If you want to combine Epics from both project types, an example of such a query would be: _{color:#DE350B}"Epic Link" = NPC-6 OR parent = NJDP-5{color}_ This work can now be selected as a column in the Global Issue Navigator and exported from Jira. !Screen Shot 2019-12-12 at 9.57.20 am.png|thumbnail! !Screen Shot 2019-12-12 at 9.58.59 am.png|thumbnail! Regards, Nathan Sturgess nsturgess@atlassian.com Product Manager, JIRA Platform {panel} h3. Original request description WIth the deploy of the epics and linking the issues to the epics at the Next-Gen projects we can't use the JQL to return issues that are associated to an epic as we can do for classic projects. h3. Steps to reproduce # Create a next-gen project # Create an epic # Associate multiple issues to the epic # Go to Issue Navigator and try to perform the search by Epic Link referencing the Next-Gen epic # No results are displayed h3. Expected results Return the list of issues that are linked to the referenced Epic h3. Actual results Use {{parent()}} function to show the child issues of the Epic. Example: {code} parent = EPIC-123 {code} |
New:
{panel:title=Atlassian Status as of 12 December 2019|borderStyle=solid|borderColor=#3C78B5| titleBGColor=#3C78B5| bgColor=#E7F4FA}
Hi everyone, Customers can query on Next-gen epics using the _{color:#DE350B}parent ={color}_. If you want to combine Epics from both project types, an example of such a query would be: _{color:#DE350B}"Epic Link" = NPC-6 OR parent = NJDP-5{color}_ The _Parent_ field can now be selected as a column in the Global Issue Navigator and exported from Jira. !Screen Shot 2019-12-12 at 9.57.20 am.png|thumbnail! !Screen Shot 2019-12-12 at 9.58.59 am.png|thumbnail! Regards, Nathan Sturgess nsturgess@atlassian.com Product Manager, JIRA Platform {panel} h3. Original request description WIth the deploy of the epics and linking the issues to the epics at the Next-Gen projects we can't use the JQL to return issues that are associated to an epic as we can do for classic projects. h3. Steps to reproduce # Create a next-gen project # Create an epic # Associate multiple issues to the epic # Go to Issue Navigator and try to perform the search by Epic Link referencing the Next-Gen epic # No results are displayed h3. Expected results Return the list of issues that are linked to the referenced Epic h3. Actual results Use {{parent()}} function to show the child issues of the Epic. Example: {code} parent = EPIC-123 {code} |
| Description |
Original:
{panel:title=Atlassian Status as of 12 December 2019|borderStyle=solid|borderColor=#3C78B5| titleBGColor=#3C78B5| bgColor=#E7F4FA}
Hi everyone, Customers can query on Next-gen epics using the _{color:#DE350B}parent ={color}_. If you want to combine Epics from both project types, an example of such a query would be: _{color:#DE350B}"Epic Link" = NPC-6 OR parent = NJDP-5{color}_ This work can then be selected as a column in the Global Issue Navigator and exported from Jira. !Screen Shot 2019-12-12 at 9.57.20 am.png|thumbnail! !Screen Shot 2019-12-12 at 9.58.59 am.png|thumbnail! Regards, Nathan Sturgess nsturgess@atlassian.com Product Manager, JIRA Platform {panel} h3. Original request description WIth the deploy of the epics and linking the issues to the epics at the Next-Gen projects we can't use the JQL to return issues that are associated to an epic as we can do for classic projects. h3. Steps to reproduce # Create a next-gen project # Create an epic # Associate multiple issues to the epic # Go to Issue Navigator and try to perform the search by Epic Link referencing the Next-Gen epic # No results are displayed h3. Expected results Return the list of issues that are linked to the referenced Epic h3. Actual results Use {{parent()}} function to show the child issues of the Epic. Example: {code} parent = EPIC-123 {code} |
New:
{panel:title=Atlassian Status as of 12 December 2019|borderStyle=solid|borderColor=#3C78B5| titleBGColor=#3C78B5| bgColor=#E7F4FA}
Hi everyone, Customers can query on Next-gen epics using the _{color:#DE350B}parent ={color}_. If you want to combine Epics from both project types, an example of such a query would be: _{color:#DE350B}"Epic Link" = NPC-6 OR parent = NJDP-5{color}_ This work can now be selected as a column in the Global Issue Navigator and exported from Jira. !Screen Shot 2019-12-12 at 9.57.20 am.png|thumbnail! !Screen Shot 2019-12-12 at 9.58.59 am.png|thumbnail! Regards, Nathan Sturgess nsturgess@atlassian.com Product Manager, JIRA Platform {panel} h3. Original request description WIth the deploy of the epics and linking the issues to the epics at the Next-Gen projects we can't use the JQL to return issues that are associated to an epic as we can do for classic projects. h3. Steps to reproduce # Create a next-gen project # Create an epic # Associate multiple issues to the epic # Go to Issue Navigator and try to perform the search by Epic Link referencing the Next-Gen epic # No results are displayed h3. Expected results Return the list of issues that are linked to the referenced Epic h3. Actual results Use {{parent()}} function to show the child issues of the Epic. Example: {code} parent = EPIC-123 {code} |
| Resolution | New: Done [ 17 ] | |
| Status | Original: In Progress [ 3 ] | New: Closed [ 6 ] |