Uploaded image for project: 'Confluence Cloud'
  1. Confluence Cloud
  2. CONFCLOUD-47894

The Atlassian Swag store integration on Answers is not discoverable

XMLWordPrintable

      NOTE: This bug report is for Confluence Cloud. Using Confluence Server? See the corresponding bug report.

      When we migrated to Confluence Questions form OSQA, we re-implemented the ability to earn and redeem stuff from the Atlassian Swag store. The UI to redeem these items can be accessed from the user's own profile page in Confluence. However, there's a few issues with this:

      1) The URL is https://answers.atlassian.com/plugins/swag/myswag.action - not very memorable. We should consider aliasing it to something like "answers.atlassian.com/swag", like it was on the old system.

      2) The Confluence user profile is buried pretty deep in Atlassian Answers due to the fact we're operating Confluence Questions in "standalone" mode. It takes 2-3 clicks to find the swag UI from the Answers homepage.

      3) Users aren't notified when they are eligible to claim new items of swag. We need to rely on the user checking back regularly to know when they've earned something.

            [CONFCLOUD-47894] The Atlassian Swag store integration on Answers is not discoverable

            Ryan Talusan added a comment -
            Atlassian Update – 2019/Oct/15

            Hi Everyone,

            We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Timed Out.

            Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Confluence team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details.

            We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication.
            Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments.

            Thank you,
            Ryan Talusan
            Confluence Cloud Ecosystem

            Ryan Talusan added a comment - Atlassian Update – 2019/Oct/15 Hi Everyone, We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Timed Out . Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Confluence team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details. We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments. Thank you, Ryan Talusan Confluence Cloud Ecosystem

              Unassigned Unassigned
              jclark@atlassian.com Joe Clark
              Affected customers:
              0 This affects my team
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: