Hi All,
We have app logic that relies on the avi:jira:updated:issue trigger module to handle every issue update event. In our development environment, the event triggers instantly, allowing us to capture the changelog from the event log immediately. However, in the production environment, we are experiencing a delay of up to 1 hour before we receive the changelog. We haven't found any documentation on changing the frequency of these events. Is there an alternative method to achieve immediate retrieval of the changelog upon an update event trigger?
Hi @balajiar , and welcome to the Atlassian Community
The execution of all jobs in Jira are controlled from the Scheduler Administration page. It could very well be the case that the interval / cron settings for handling your event are not the same between your two instances.
Hope this helps get the events flowing,
Dick
By voting for helpful posts and marking answers to your question, you're helping people with similar questions find a solution more quickly. Sharing is caring applies to knowledge as well :)
Hi @balajiar,
The why behind the interval length is a mystery to me.
That's why I was trying to steer you to the place where it might be defined, so you can edit it.
Hope you can squeeze the waiting period this way,
Dick
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I am working on achieving instant updates to fields whenever any field is modified by a user. For example, if a user edits the estimated value, it will instantly update some custom fields. The suggested functionality is good, but I don't have Jira admin access, so I can't see the scheduler admin page or control schedules. Instead, I am thinking of accomplishing this with the Forge app.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Either which way you're achieving the instant feedback upon change, I would definitively advise you to contact your admin about your needs, as you are putting a bit more strain on the system (always handy to keep your admin happy :) ).
Dick
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you for the advice. I'll make sure to reach out to my admin to discuss my needs and the potential impact on the system. It's always a good idea to keep them informed and happy!
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.