Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Interests
See all
Community resources
Top groups
Explore all groups
Community resources
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Join now to unlock these features and more

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Get started Tell me more
Atlassian Community about banner
4,551,886
Community Members
 
Community Events
184
Community Groups

Calling REST API from python issues with latest version of Jira

Vincent Guesdon
Vincent Guesdon
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Get involved
May 15, 2023

Hi,

 

where I am working, we use a python API to get tickets info, create and delete on jira using the REST API.

Everything was working fine until the company update jira to a newest version of jira
we went from v8.3.5 to v8.20.10

 

now when we use the REST API to create or delete a ticket, then after the server gave it's response we have no guarantee how long before a search will actualy work properly on it which is highly problematic.

 

the timing seems completely inconsistent, sometimes just calling delete then search for the ticket actually works and return something instead of a proper not found

and the info that it returns can be completely messed up. Any idea how to solve this that doesn't required to come back to an older version of the jira server ?

Answer
Watch
Like Be the first to like this
62 views

0 answers

Suggest an answer

Log in or Sign up to answer
Jira
Jira
TAGS
AUG Leaders

Atlassian Community Events

See all events