Uploaded image for project: 'Atlassian Marketplace'
  1. Atlassian Marketplace
  2. MP-187

Updating Forge app details in developer console or markeplace does not propagate to end-users

    • Severity 2 - Major
    • L

      Issue Summary

      After deploying a Forge app to production, if the developer updates the app details either through the developer console or through the marketplace listing, the updated details don’t propagate to all customer and end user touch points.

      This includes the following fields:

      • App name
      • Company/Department
      • Privacy link
      • Avatar and header images

      Because of this the consent screen doesn't show the updated values to the end-users allowing access to the app.

      Steps to Reproduce

      1. Build a Forge app and deploy it to prod
      2. Change, for example, the app name
      3. Install the app on a test site

      Expected Results

      The consent screen shows the new/updated app name

      Actual Results

      The consent screen shows the old app name

      Workaround

      As a Forge developer or Marketplace partner, please raise a ticket with the Ecosystem Support team for the details to be updated by Atlassian and quote this Bug report or FRGE-525 for reference.

      Link to the portal option: https://ecosystem.atlassian.net/servicedesk/customer/portal/34/group/106/create/567

            [MP-187] Updating Forge app details in developer console or markeplace does not propagate to end-users

            We have added the reported issue to our backlog and plan to address it in the coming months.

            Anjali Chawla added a comment - We have added the reported issue to our backlog and plan to address it in the coming months.

              dsood Deeksha Sood (Inactive)
              dbonotto Dario B
              Affected customers:
              0 This affects my team
              Watchers:
              9 Start watching this issue

                Created:
                Updated: