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
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
My organization frequently uses the /iql/objects endpoint in the Assets REST API and specifies the includeAttributesDeep query parameter to be more than 1. Getting multiple levels in the single search result is highly convenient. Documentation now shows that calls that contain includeAttributesDeep are deprecated. Is there any alternative to this functionality besides making several API calls to get each object?
Link to documentation:
The deprecation of
includeAttributesDeep in the Assets REST API of Atlassian presents a challenge, especially since you’re relying on it to fetch multiple levels in a single search result. Here are a few potential alternatives and workarounds to consider:
First and foremost, review the most recent version of the Atlassian API documentation. Atlassian might have introduced new query parameters or endpoint features that could serve as a replacement for
includeAttributesDeep. Sometimes, API updates include new functionalities that are meant to replace deprecated features.
While this isn’t the most efficient method, making several API calls to retrieve each object level is the most straightforward workaround. You can optimize this approach by:
Implement custom logic in your application to aggregate data from multiple API calls. While this increases complexity on your end, it allows for more control over data handling and aggregation.
Atlassian might have introduced new features or endpoints in the Assets API that could replicate the functionality of
includeAttributesDeep. Look for features like expanded objects, nested queries, or advanced filtering options.
Sometimes third-party plugins or tools available in the Atlassian Marketplace offer extended functionalities or alternative ways to interact with Jira data. These tools might provide a workaround for the deprecated feature.
If the documentation isn’t clear or you’re unable to find a suitable alternative, consider reaching out to Atlassian Support. They might provide insights into upcoming features or recommend best practices post-deprecation.
Keep an eye on discussions in the Atlassian Community forums. Other users might be facing similar challenges and could share their solutions or workarounds.
Provide feedback to Atlassian about the impact of deprecating
includeAttributesDeep. User feedback can sometimes influence product updates or lead to the introduction of alternative features.
It’s crucial to plan for changes in your implementation strategy to accommodate these API updates. While direct replacements may not always be available, these alternatives can help maintain the functionality of your system with some adjustments. Good luck, and I hope one of these suggestions helps you navigate this transition! 🚀🔧📊