You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I saw the notifications from Atlassian that Epic Link and Parent link are being consolidated to Parent, and some of the documentation refers to IssueParentAssociation.
Given that we are in the period where both are supposed to be working:
"During the deprecation period, the Epic Link
and Parent
values will be returned alongside IssueParentAssociation
in order to facilitate migration."
Why can't I see "IssueParentAssociation" or "Parent" fields (or custom fields) in my JIRA Classic (cloud) projects?
It is only the REST API that is changing, the changes do not apply to these fields in the Jira UI and JQL based on the email that was sent out to customers. Here is the announcement on the Developer Community.
Yes, and...to what Mikael notes:
If you read through that thread you will also see that automation rules' smart values are impacted. Atlassian notes they will attempt to automagically update what they can, and other rules may require manual updates; Atlassian noted a plan to send out more information on that when it occurs.
Kind regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Is there any update as to when this update will roll out? I'll be happy when I don't have to specify "Parent Link" vs "Epic Link" on the Create/Edit/View screens...
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.