nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Is there a lag time between updating JIRA tickets and using API? assignee is NULL

letsbuild

I'm trying to build a dashboard using the Jira API. I'm able to get my list of issues using:

/rest/api/3/search

But when I update the assignee, it doesn't take effect into the API. the list of issues still says assignee: null

I'm using nextjs, and I noticed that if I delete the .next folder, and rebuild the site, the API data is updated. I'm trying to understand why this is happening? Or why the API response is being cached. I wanted to make sure that if there's an update in JIRA, it'll be updated in API without having to delete the .next folder.

Accepted answers

Nic Brough -Adaptavist-

Welcome to the Atlassian Community!

No, there is no lag - if you make a REST call to update an issue, then the issue will be updated before you get the response saying it was successful.

All comments

Nic Brough -Adaptavist-

Welcome to the Atlassian Community!

No, there is no lag - if you make a REST call to update an issue, then the issue will be updated before you get the response saying it was successful.

letsbuild

Hmmm, oh okay thanks, must be my implementation or some kind of caching issue with nextjs. thanks

letsbuild

@Nic Brough -Adaptavist- i'm kind of curious - how would you approach streaming the API call? like so if there's an update from JIRA, it'll also update on NextJS client side?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud