Forge confirmation card sometimes renders without content in Jira

[Venkateswar Kasa]

Hi Team,

We have developed an Atlassian Forge app that generates test cases and test steps for a Jira user story.

As part of the workflow, before creating the test cases, we display a confirmation card to the user. This card is expected to show details such as:

• Test summary
• Test description
• Project key
• User story reference
• Preconditions and conditions

The user is required to review this information and confirm before proceeding.

---

Issue

We are experiencing an intermittent issue where:

• The confirmation card is displayed, but
• The content inside the card is missing

This behavior is not consistent — sometimes the card renders correctly with all details, and sometimes it appears without any content.

From the screenshots (attached), you can see:

1. In some cases, the confirmation card appears empty without any data.
2. In other cases, the card is rendered correctly with all expected fields populated.

---

Expected Behavior

The confirmation card should always display the generated test case details consistently

user confirmation.

before user confirmation.

[Dr Valeri Colon _Connect Centric_]

@Venkateswar Kasa this sounds like an intermittent Forge rendering/state issue rather than expected behavior. I’d check whether the card is rendering before the generated data is available, especially if values are loaded async. Add loading/empty states, log the payload passed into the confirmation card, and confirm whether this is UI Kit or Custom UI. If the payload is present but the card renders empty, I’d open a ticket with logs, app ID, environment, and timestamps.

[Venkateswar Kasa]

Hi @Dr Valeri Colon _Connect Centric_ ,

Thank you for the response. Please let me know if any details are needed from my side.

[Dr Valeri Colon _Connect Centric_]

You're welcome @Venkateswar Kasa. Since the issue is intermittent, try to determine whether the data is missing or whether the UI is failing to render it.

A few things to check:

• Compare Forge logs from a successful run and an empty-card run
• Verify whether the payload contains the expected values when the card renders empty
• Look for patterns (specific users, larger test cases, certain projects, peak usage times, etc.)
• Check whether introducing a loading state or delaying the render changes the behavior

If you can show that the payload is present but the card occasionally renders empty, that would be useful evidence for Atlassian Support Team (this is the user community). Otherwise, you may find the root cause in the app before needing to open a ticket.