Issue Summary

In several Confluence event payloads (including for pages, blogposts, whiteboards, databases and smartlinks, the user resource found within the content->history object appears to have incorrect values. Specifically, the fields accountId, username, publicName, and displayName are all populated with the same value (the accountId). This is misleading since both publicName and displayName are expected to contain a human-readable name for the user.

Steps to Reproduce

1. Create a forge app with below files:

export async function run(event, context) {
    console.log('inside trigger function');
    console.log(JSON.stringify(event, null, 4));
    console.log(JSON.stringify(context, null, 4));
}

modules:
  trigger:
    - key: page-updated-trigger
      function: trigger
      events:
        - avi:confluence:updated:page
  confluence:spacePage:
    - key: hello-world-space-page
      resource: main
      resolver:
        function: resolver
      render: native
      title: hello-world-test
      route: hello-world
  function:
    - key: resolver
      handler: index.handler
    - key: trigger
      handler: trigger.run
permissions:
  scopes:
      - read:confluence-content.summary
resources:
  - key: main
    path: src/frontend/index.jsx
app:
  runtime:
    name: nodejs22.x

1. deploy the app and run forge tunnel to observe the traffic

1. Update the page in confluence. It should result in the payload to be logged in forge tunnel terminal.

1. observe the values (accountId, username, publicName, and displayName) under content > history > CreateBy. 

Expected Results

The values for publicName and displayName should have human readable values

Actual Results

The keys: username, publicName, and displayName all contain the accountId.

Workaround

Make a request to Get User API from the trigger to get the values