Deprecation of Epic Link is approaching (30th of November)
Will the Epic Link field disappear from the screen settings? Will it be still mandatory to have an Epic Link added to the Create issue screen in order to receive the parent field in the issue-created webhook payload?
In Issue Templates for Jira Cloud we are trying to setup child templates whenever a new child template is created ( e.g. Story template under Epic template).
In Jira, in the issue view you can simply click on “Add a child issue” to add a new issue under an epic. It doesn’t matter whether you have an Epic Link added to Create screen or not. However there is an inconsistency in the data we are receiving in the issue-created webhook. If the Epic Link is not added to the Create screen then the parent field is missing in the payload.
Is it something that is already reported and will get fixed?
@KonstantinK could you look into this?
Hi @maciej.dudziak, thanks for reporting this to us.
My understanding is that “parent” and “Epic Link” are not persisted correctly, hence they are missing from the webhook. We already have the fix in place, just need to roll it out. Once this happens, “parent” should appear in webhooks regardless of the screen configurations.
Latest update on the deprecation: Deprecation of the Epic Link, Parent Link and other related fields in REST APIs and webhooks - #86 by KonstantinK
hi @KonstantinK, when can we expect the flag to switch off the old Epic link fields to be available for testing?
Hi @hareeshr1179, thanks for your message, and welcome to Atlassian Community!
We plan to provide such a flag so that our Marketplace partners could test their changes without the deprecated fields. Once this becomes available, we’ll post a comment in Deprecation of the Epic Link, Parent Link and other related fields in REST APIs and webhooks. Please subscribe to new comments in this post to stay up-to-date and get notified once this becomes available.
We understand that this may not allow enough time for you to test your changes. We will monitor the usage of the old fields, and we will switch them off at any point after 30 Nov, when our monitoring indicates that it is safe to do so. We will also make sure to allow enough time for our Marketplace partners to test their apps with these fields switched off. We will not switch these fields off across production instances until we make sure that our Marketplace partners have had an opportunity to test their apps with these fields switched off.
hi @KonstantinK, any updates on when the feature flag will be available for testing Epic link deprecation?