@glewandowski the Search Issue IDs using JQL a new API previously proposed, has now been shown as depreciated? just wanted to confirm will it be actually removed?
Hello,
Can we expect for any of the abovementioned concerns to be addressed before the deprecation date? Or it’s just another case of “RFC as early announcement” to fill a checkbox in internal process?
Ben, we appreciate your input on this matter. However, at this moment, we are unable to confidently provide such a limit. The number 100 remains aligned with the limits established by the previous search endpoints. The documentation for the Connect scope was generated incorrectly, but this issue has now been resolved.
We have decided to support all expansions that were previously available with the old endpoints. The documentation wasn’t generated properly, but this issue has now been resolved.
1 Like
Yes, that’s correct. Adoption of this endpoint was very low, and it doesn’t offer any additional features compared to the new endpoints we just introduced. Therefore, we have decided to deprecate and remove it.
I’m reposting the resolution summary as a comment for visibility purposes, as some might not have noticed the update in the original post.
Update
Thank you so much for your feedback! We really appreciate you taking the time to share your thoughts with us.
At this moment, we can’t offer larger batch sizes. We know that eventual consistency might be a bit confusing for some of you. We’ll put together some helpful tips on how to work with it. We’re also looking into the possible options forexpandin the new APIs. Thanks for your understanding!
The deprecation announcement will be slightly delayed, and you can expect to hear from us about it in mid to late October. After a 6-month deprecation period, the old APIs will be phased out.
As some of you might have already noticed, the endpoints have been deprecated, and the deprecation notice contains migration guidance.