We have rolled out the fix for JSWCLOUD-22914 to all production customers.
This bug should be no longer reproducible starting from Jun 9, 2022.
This means that the parent field can now be used when creating an issue at the Epic level (level 1) if the parent belongs to the hierarchy level above (configured via Advanced Roadmaps).
Please note that the other bug [JRACLOUD-78657] Inconsistent rest api behaviour when setting parent issue when epic link is not on update screen - Create and track feature requests for Atlassian products. hasn’t yet been fixed. We will update the public bug ticket once it’s been resolved.
Thanks!
UPDATE 04/10/2022. We’re working on unblocking the Marketplace partners to be able to test Change 6. We will update you all soon with the results of it. We will make sure that there is enough time for everyone to test their changes.
Update (7 October 2022).
In order to give our Marketplace partners a better experience in testing Change 6 (changelog items in webhooks), we decided to change the rollout plan for it to return both OLD and NEW changelog items in the SAME webhook event. Originally we announced that we would only return either OLD or NEW changelog.
We plan to rollout Change 6 to Early Adopters / Jira Ecosystem Beta group, and later to all other instances, within a month from now. 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. If you think you won’t be able to make the required changes to your app before 30 Nov, please let us know.
The bug [JRACLOUD-78657] Inconsistent rest api behaviour when setting parent issue when epic link is not on update screen - Create and track feature requests for Atlassian products. will also be fixed before 30 Nov.
1 Like
Just a heads-up that the bug JRACLOUD-80531 caused the endpoint /rest/api/2/issue/{issueIdOrKey}/changelog return a duplicate IssueParentAssociation item for all Epic Link / Parent Link changelogs. This bug was introduced 3-4 months ago.
The fix for it will be rolling out to production starting now. It will stop these duplicates from being generated for new changelogs. More details, especially on how it affects Parent Link, can be found here.
Only the endpoint /rest/api/2/issue/{issueIdOrKey}/changelog is affected.
The bug did NOT affect webhooks. The fix will NOT affect webhooks. They will continue working as described in Change 6 of this notice.