Updating Issue-UI after update per API (REST PUT)

I have trouble or maybe misunderstanding how it work, that the UI is updating after I sent a PUT to update the issue per rest.
I create a timerecording connect-app. After creating a timerecord, the ‘remainingEstimate’ will also be updated.
What I expect, is that the field shows the new value, but it does it only after refresh the issue. (for information, the PUT is working as expected)
My PUT: (“atlassianApiCall” is a helper I created)

    url: `/rest/api/3/issue/${issueInformation.issueId}`,
    type: "PUT",
    data: {
      fields: {
        timetracking: {
          remainingEstimate: "2h",
          originalEstimate: "1d",

What I don’t want to do is .then(() => AP.jira.refreshIssuePage());
Because it restarts the connect-app in issueContext and that is not a great UX.

Welcome to the Atlassian Developer Community, @MarkusOrt.

For this use case, the only way that I know of is calling refreshIssuePage(), however, you explicitly mentioned that it is not something you want to do.

There are a couple of similar feature suggestions for your reference: JRACLOUD-76943 and JRACLOUD-78008


1 Like

Thank you @iragudo

Just to get the pressure high to Atlassian :stuck_out_tongue:
I already made same App (extension) for Microsoft Azure DevOps. When there I make a WorkItem (respective issue) update per REST PUT, the UI updates the fields I changed.
So I guess they working with SignalR (websockets).
Maybe this is a thing you can take to the developers in next sprints? :slight_smile:

I will stick to suggested features.
Thanks a lot!