Konstantin Kulishenkov Atlassian Team

Hi @Kim-Stacey Kidder and @Ethan_Heimstead - Jira Automation was updated to work with the "Parent" field back in 2023, so it won't be affected, however we ask all admins to ensure that none of their Automation rules directly reference the deprecated fields as smart values. We have communicated this deprecation to the app…

Hi @Julio Bohler The "parent" field does not have a custom field ID. To reference it in Jira API / webhooks (I assume ScriptRunner uses that), we need to use just "parent", please see examples…

Hi @julia.pacula! Thanks for reporting this. We're currently fixing this problem, it's tracked at https://jira.atlassian.com/browse/JSWCLOUD-26119, which also contains the workaround. The fix will be released at some point after the holiday period. Thanks, Konstantin

Hi @Florent Baret and @[deleted]! Just to confirm - is this about webhook events in Jira? The "issue_updated" event is fired when the issue parent has been changed, and it contains the "IssueParentAssociation" changelog item, that represents the "Parent" field. It appears there alongside "Epic Link" or "Parent Link". Refer…

Hi @Brian Lamb and @Chris Thomas, thanks for reporting this to us. Please refer to the public bug https://jira.atlassian.com/browse/JSWCLOUD-26109, which we use to track this problem. It has the "Workaround" section with some details on what to do to temporarily resolve this. Thanks, Konstantin

Hi @Paddy Walsh, thanks for reporting this issue. Jira has internal validation for the "Parent" hierarchy level. It will not allow to create invalid hierarchies, so there's no need for any custom validation to achieve that. Generally, we expect the existing workflow validations to continue working as is. Please create a…

Hi @Mélanie Liguet, please refer to this announcement for the REST API changes: https://community.developer.atlassian.com/t/deprecation-of-the-epic-link-parent-link-and-other-related-fields-in-rest-apis-and-webhooks/54048 Yes, your company should modify the bots to only use the new functionality from the announcement…

Hi @Antoine _Klee Group_, thanks for reporting this issue with Transition Screens not having the Parent field added automatically (where there was Parent Link or Epic Link). The fix has been implemented and is currently being rolled out, ETA next week. Until then, the workaround is to add Parent to these screens manually.…

Hi @Steffen Edinger, would you be able to create a support ticket with this problem so we could investigate that in the affected Jira instance? I've tried reproducing this, having switched my user language to German. The Parent (Übergeordnet) dropdown worked correctly for me - it was not empty. I tested that on Issue View,…

Hi @Aline Chapman, thank you for reporting this problem. The changes we're rolling out are backward compatible, so all existing Automation rules that involve Epic Link or Parent Link will continue working seamlessly. The same applies to Worflows and Jira Expressions used in the JMWE validator. We have not been able to…

Hi @Yatish Madhav - yes, these changes are for Premium, except for "Dynamic issue type names at the Epic level" which I believe should work on Standard as well. Thanks, Konstantin

Hi @Yatish Madhav! Generally, we recommend checking "Atlassian Cloud Documentation blog posts" for updates on what features are currently rolling out. To access them, in Jira, click the question mark icon on the top right panel, and then click "Find out what’s changed in Jira". The changes described on this page (Custom…

Hi @Paul Thomson thanks for your feedback. We're currently looking into adding support for a "universal" parent field in Jira Automation, that would work for all issue types. We will communicate if this will be released. Thanks, Konstantin

Hi @Campbell, historically the issue type dropdown in the "Child issues" panel has shown all issue types, not just the ones with the hierarchy level below. We've been tracking this bug internally, but I've just created https://jira.atlassian.com/browse/JSWCLOUD-25484 for external visibility. This bug is not caused by our…

Hi @Paddy Walsh! That's correct, for now, the field "Parent" is not yet available. It will appear in Jira after this is released. should I use 'Parent Link' to link subordinate issues to them Until the "Parent" field gets released, this is the only way to do it, yes. "Epic Link" should be used for the system epic type…

Hi @Paddy Walsh! only the special system 'Epic' would appear in various places where Epics are used - can you confirm this And would the 'Epic Link' field only work for links to system epics Yes, both statements are correct. For now, to set a "non-system epic" (other issue types at level 1) as a parent, the "Parent Link"…

Hi @Campbell, thanks for your feedback. We aim to provide consistent experience in Jira Issue View between the "system" epic issue type, and other issue types at level 1. The "system" epic issue type does not allow the creation of subtasks from the Issue View. It's still possible to create subtasks using the [+] button in…

Hi @[deleted] thanks for your feedback! If you set up a SAFe-like hierarchy, Epic -> Feature -> Story, will Epic and Feature both have hierarchy level 1 or will Epic be at level 2? You can configure it either way, but to be able to set an Epic as the parent of a Feature, you'll need to rename level 1 (and the default Epic…

Hi @Dave Mathijs! We've kept the original behavior around additional epic-level custom issue types as is: they can be added via Settings > Issues > Issue type hierarchy, but they will not be treated as epics by Boards, Epic reports, and other epic-specific functionality in Jira. Issues with these types can still be used as…

Hi @Darryl Lee and @Bill Sheboy Atlassian plans to migrate the affected smart values by 31 May 2022 so that Automation rules won’t break. If there are any edge cases we're unable to migrate, we'll make sure to communicate this closer to the time. I've updated my original post with these details. Thanks, Konstantin

Hi @Darryl Lee and @Bill Sheboy thanks for raising this. We're very keen to hear any feedback from our Community on this announcement. The reason we've closed the comments here is that we'd like to keep the discussion to Developer Community Atlassian only. Having a single source of truth would allow us to reply to all…