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

Improve error handiling when encountering a user that no longer exists

    XMLWordPrintable

Details

    • 2
    • 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.

      Currently JIRA will stack trace when encountering a user that does not exist. We should catch this exception and handle it more gracefully ( perhaps by allowing the ticket itself to still be transitioned or edited while displaying a warning message )

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-15806 Selecting User Reporter that does not exist during bulk move results in 500 page.

          • Low - Low priority issues
          • Closed
          relates to

          Suggestion - JRACLOUD-21070 Improve error handiling when encountering a user that no longer exists

          • Closed

          Activity

            People

              Unassigned Unassigned
              jcurry Jeff Curry
              Votes:
              2 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: