Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
Level
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

API 2.0 Breaking Changes Coming to 10.92

As we continue our journey to improve the usability and performance of our API, we want to keep you informed about some changes coming to the API 2.0 in version 10.92 and beyond so you can plan accordingly.

These updates will bring consistency to our API experience, improve processing speed, and enable new features down the road. Your API calls will have to be modified to accommodate these changes.

If you have any questions on these changes, reach out to your Technical Account Manager, or just comment on this post!

brokeConnection.png

 

Change 1: Capabilities API - Property Re-name and Deprecation

We are making these changes to improve usability and consistency for Capabilities API.

Property re-name:

  • complexity renamed to kanoComplexity

  • certainty renamed to kanoCertainty

  • programId renamed to primaryProgramId

Property deprecation

  • lastModifiedDate will be deprecated. Please use the existing lastUpdatedDate property instead.

We will also add a new additionalProgramIDs property.

 

These changes will be included in 10.92 (with updated Swagger docs), deployed to test environments on April 10, 2021, and to production instances on April 24, 2021, per our release calendar.

 

Important note:

We plan to make similar changes to other API objects in the future to address usability gaps.

When we are ready for the next batch of updates we’ll share another post like this.

 

 

Change 2: Enforced API Token Formats

These changes will improve your API performance and enable better logging features in the future.

Current supported token formats:

  • tokenkeynumber123

  • user:Id|tokenkeynumber123

Future supported token formats

  • user:Id|tokenkeynumber123

 

In the future, we will only support the format for API Tokens that includes your user:Id. The exact enforcement date for this change is TBD, but we strongly encourage that you update your API calls with this new format now. One immediate benefit you get is better performance because this token format helps our API process authentication much faster.

You can grab this token in Jira Align on the user profile (top left) > Edit Profile > Account Details > API Token > API 2.0 Token.

 

Important note:

API 2.0 will only support the API 2.0 tokens displayed in the UI.

 

Thanks for your help!

 

0 comments

Comment

Log in or Sign up to comment
TAGS
Community showcase
Published in Jira Align

Helpful hints if you're rolling Align out to your entire enterprise

(Or, What to expect when you’re expanding.) Once you've completed your Jumpstart, or your initial assessment of Jira Align, you'll start to think about how you can roll it out to the rest of your e...

939 views 3 22
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you