Links from marketplace listings to Community forum are outdated

XMLWordPrintable

    • Severity 2 - Major
    • Visual regression testing
    • S

      Issue Summary:

      The links that exist on all marketplace apps are outdated.  These should be updated in order to correct some problems they currently pose to end users seeking support for these apps in the Atlassian Community Forum.

      Steps to Reproduce

      1. Visit a marketplace app listing and go to the Support link, for example:
        https://marketplace.atlassian.com/apps/1233252/sprint-reviewer-pro?hosting=cloud&tab=support
      2. Currently the example has a community link of
        https://community.atlassian.com/t5/custom/page/page-id/create-post-step-1?add-tags=atlassian-marketplace%2Caddon-com.cloze.jira.plugins.sprintreviewerpro%2Ccloud
        But instead that link to community should be more like this:
        https://community.atlassian.com/forums/forums/postpage/board-id/app-centralqanda-board?add-tags=atlassian-marketplace%2Caddon-com.cloze.jira.plugins.sprintreviewerpro%2Ccloud
        Following the first link can still create a community post, but it is defaulting into asking the user for their site info. In this case we don’t want to do that, because it will end up misdirecting their post to the wrong collection in the community forums.

      Expected Results

      When clicking on the 

      Engage with Atlassian-hosted discussions where other customers discuss about apps.

      link, we expect that the page we are taken to will prompt the user directly for their question related to that app, and pre-populate the necessary tags.

      Actual Results

      Currently using those links takes the user to an incorrect page that prompt them to select which product/site.  This isn't including the proper tags, and it doesn't create the question necessarily in the correct community forum collection

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

            Assignee:
            Saurabh Sharma (Inactive)
            Reporter:
            Andy Heinzer (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: