Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-27484

Give reason why remote issue link "Failed to load"

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Won't Do
    • None
    • None
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

    Description

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      If the remote issue link cannot be rendered (e.g. the issue on the remote server does not exist, the remote server is down or the application link has been deleted), we simply say "Failed to load" and print a message in the logs. Instead, it would be better if we gave the reason in the UI, removing the need to add a message to the logs.

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-27342 Get Huge exception in the logs if a remote link is associated with an applink that no longer exists.

          • Low - Low priority issues
          • Closed

          Suggestion - JRACLOUD-27484 Give reason why remote issue link "Failed to load"

          • Closed
          links to

          Web Link Why Jira displays "Failed to load" message for people that do not have access to a remote jira instance?

          Activity

            People

              Unassigned Unassigned
              gsmith@atlassian.com Graeme Smith
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: