Uploaded image for project: 'Atlassian Access'
  1. Atlassian Access
  2. ACCESS-1340

Improve error handling when uploading emojis due to configuration

    XMLWordPrintable

Details

    • 2
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

    Description

      Summary

      When looking to add a custom emoji via the site administration (I.E. https://site.atlassian.net/admin) > Emojis, if the Allow people to add custom emojis toggle is off, although the user will be able to select the file, give it a name and tap the Upload button, a warning with an upload failed message will be displayed:

      From the browser's console, a "403" is triggered and also an error message:

      Request URL: https://admin.atlassian.com/gateway/api/emoji/CLOUD-ID/site/token/upload
      Request Method: GET
      Status Code: 403 
      Remote Address: XXXXXXXXX
      Referrer Policy: strict-origin-when-cross-origin
      
      Unable to upload emoji: No media api support is configured
      

      Suggestion

      Since the error message is not clear, this is a suggestion to provide a message stating that the option to allow custom emojis is toggled off, needing to be toggled on.

      This way, it quickly allows the administrators to understand what is the nature of the issue. Alternatively, not allowing the upload to happen until the option is toggled on would help as well.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              gdecampos Giuliano C.
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: