We have requirement to capture Jira ticket status change into our system/database
We are creating tickets programitacally (using rest API) and we would like get notified for any change in status for those tickets so we can update the same in our database.
One way is polling Jira for status which may not be seamelss experience.. Is there any way that Jira provides mechanism to get such ticket status updates?
Try this - Set up a filter that shows issues that are in your scope that have been updated in the past "X" days or hours.
updatedDate >= -4h
Then set up a subscription to notify anyone who needs to know. This is done under the "filter details option".
But -- if you're creating the tickets using an API, you can skip the Filtger Subscription and simply use the rest endpoint of issue search to identify them in whatever tool needs to know.
rest/api/3/search/jql=updatedDate>=-4h
Good Luck
Hello @Naveenkumar Goudar
You used the word 'we' a number of times, inferring you are part of a group or team of developers.
It's strange that not one single person in your entire team was capable of using Google to search for the answer to that Frequently Asked Question. When you Googled "How can I get a notification of issue change events in Jira Cloud?" didn't anyone in your team find all the documentation about event notification schemes, or creating and listening for webhook events?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
notification schemes - AFAIK it is just email.
webhook - I am aware, issue is AFAIK webhook's expire in 30 days.. need to keep extending life of webhook
So was exploring if there is any more ways
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Well, if you already knew about the existence of those two mechanisms for getting issue status updates, why ask the question "Is there any way that Jira provides a mechanism for issue status updates?".
Also, if just one person on your team were to have USED GOOGLE on the topic of the circumstances under which webhooks expire after 30 days, they would have found the answer to that question too!
It seems your question is now changing direction, so I don't think I'll be of any further assistance to you.
Good luck.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
bad day?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.