The use of ‘Epic Link’ is still allowed via JQL, but as has been described in the deprecation documentation, that is only so as to not break existing JQL queries that use it. The same applies to the UI… until the change-over is complete this year, as per this documentation and the new configuration starts being rolled out.
The change-over is being done over a period of time, so it would be reasonable to assume SOME Jira instances still have the old configuration and SOME Jira instances now have the new configuration.
What happened when you stopped using Epic Link for those ‘some’ instances that are problematic? Did the problem go away?
When you looked at the UI of those problematic Jira instances, do they have the new UI with Parent or the old UI with Epic Link?
When you tried doing a JQL search via the UI of those problematic Jira instances, did they allow the old Epic Link field to be used?
@david2 Yes it’s a problem that seems to be separate from the ‘Parent link’ outage from yesterday.
The documentation mentioned by @sunnyape says that Atlassian will start removing Epic links from the UI and partly from JQL in 2023 but the corresponding developer notice explicitly says that JQL changes are out of scope:
Will Epic Link or Parent Link be removed from JQL?
No. Also, we will add full company-managed project support to the parent JQL, and it will become the recommended way of searching for issue’s children in JQL. Read our Community announcement about it .
Note that all changes to JQL (including the full support for parent JQL) are out of the scope of this notice and will be released separately.
@sunnyape I’d love to have access to the instances to answer the questions 2-3 JQL without epic link works fine.
I just had a quick look at a couple of Jira instances that I’m working on, and they’re all still using the old config with a UI with Epic Link showing, so it looks like the change-over hasn’t started in our region yet.
Are you not able to contact the sys admins for those few problem Jira instances and ask them how their instance is configured? It would a great way to know for sure. You could also run a query against the Get field configurations endpoints to find out what fields they have, what screens are using them and which projects are using those screens. You’d then know if the Epic Link field is active and on the appropriate screens for the projects you are running the JQL against.
Personally, I stopped using both Epic Link and Parent Link fields about 6 months ago, when the deprecation notice came out, so all my code now uses Parent field and I’ve not had any issues, plus I’m future-proofed when the change comes to my region.
Good luck with finding the answer, and please post it here when you work it out.
Thanks for confirming that Epic links are still supported in JQL.
Are any changes going to be communicated to vendors in the future? We are currently using ‘Epic link’ to identify issues that are children of epics in company managed projects. We could potentially use ‘parent is not empty and hierarchyLevel=0’ but this also matches issues from Advanced Roadmaps hierarchy because hierarchyLevel is set to 0 for higher levels above the epics.