[BUG] Jira issue context dynamicProperties

Forge Forge UI Kit and Custom UI
, , ,
1

In Jira issue context, dynamicProperties can be specified to show badge/lozenge. Refer to this page https://developer.atlassian.com/platform/forge/manifest-reference/modules/jira-issue-context/#dynamic-properties.

However, the function doesn’t seem to get called recently, and the badges/lozenges are also not appearing. I’m fairly certain it was working before. Was there a recent change?

2

@allantl, did you manage to resolve this? I’m unable to get it to work.

Below is my module definition in the manifest.yml. The definition passes the Forge CLI validation, but the dynamic properties function is never called, and no badge is shown in the UI.

modules:
  jira:issueContext:
    - key: my-issue-context
      resource: r-forge-remote
      resolver:
        endpoint: connect-endpoint
      icon: resource:r-static;icon.svg
      title: My issue context
      label: My label
      status:
        type: 'badge'
        value:
          label: '0'
      dynamicProperties:
        function: f-NeVU2u

Appreciate any ideas on what I am doing wrong.

3

I also tried removing the dynamicProperties definition and just having a static value, but that does not display anything either. I have also tried a static lozenge status, which does not display either.

5

@tbinna It works for me with the following. However, I’ve noticed that in some Jira instances, the issue context doesn’t appear at all. I’m not sure why that happens.

  jira:issueContext:
    - key: my-issue-context
      resource: issue-context
      resolver:
        endpoint: remote-app-node
      title: My title
      label: My label
      dynamicProperties:
        function: function-resolver

Forge function

export async function handler(contextPayload) {
  return {
    status: {
      type: "badge",
      value: {
        label: "0",
      },
    },
  };
}
6

Thanks, Allan. That’s strange. Our code and module definition essentially looks the same but it does not work for me. I just noticed that the badge status also does not work for the Connect module on my develpoer instance via Connect on Forge.

@atlassian Does anyone have an explanation/idea on what’s going wrong here?

7

I have created FRGE-1948 to track this issue.