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

BitBucket Imports Causes 500 Internal Error When Adding Or Editing Email Address

    XMLWordPrintable

Details

    • 1
    • Severity 2 - Major
    • Hide

      Atlassian Update – 04 July 2019

      Hi everyone,

      After reviewing the overall customer interest and impact of this bug report we have decided to close this issue down. Our analysis has shown that over time this issue hasn't collected a significant number of votes, watchers, comments, or support cases from customers and therefore has remained very low on our priority list. Given these findings we can conclude it will not be fixed in the foreseeable future and wish to be transparent about our priorities by closing it as Timed Out.

      Although we're aware this issue may be still important to those of you who were involved in the initial conversations around it, we want to be clear by managing your expectations regarding the likelihood of a fix for it. The Jira team do their best to prioritise the issues that have high and critical impact with broad pervasiveness reflected in series of different factors. You can learn more about this by reading our Bug Fixing Policy.

      To see what the Jira team is currently working on and has recently delivered see the following dashboards:

      We understand that hearing a decision like this can be disappointing, but we hope you'll appreciate our transparent approach to product priorities and communications. We will continue to watch this issue for further updates, so please feel free to share any thoughts in the comments.

      Thank you,

      Pawel Drygas,

      Jira Server Bugmaster

      Show
      Atlassian Update – 04 July 2019 Hi everyone, After reviewing the overall customer interest and impact of this bug report we have decided to close this issue down. Our analysis has shown that over time this issue hasn't collected a significant number of votes, watchers, comments, or support cases from customers and therefore has remained very low on our priority list. Given these findings we can conclude it will not be fixed in the foreseeable future and wish to be transparent about our priorities by closing it as Timed Out . Although we're aware this issue may be still important to those of you who were involved in the initial conversations around it, we want to be clear by managing your expectations regarding the likelihood of a fix for it. The Jira team do their best to prioritise the issues that have high and critical impact with broad pervasiveness reflected in series of different factors. You can learn more about this by reading our Bug Fixing Policy . To see what the Jira team is currently working on and has recently delivered see the following dashboards: Jira Server and Data Center: Recently resolved issues Jira Server and Data Center: Current work and future plans Jira Server and Data Center: Bug Fix Board We understand that hearing a decision like this can be disappointing, but we hope you'll appreciate our transparent approach to product priorities and communications. We will continue to watch this issue for further updates, so please feel free to share any thoughts in the comments. Thank you, Pawel Drygas, Jira Server Bugmaster

    Description

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

      User account creation usually requires email address field to be populated. Jira cannot handle imported user accounts without that property/field. Users that follow these instructions for BitBucket data imports and find issue imports with created with user accounts, will run into this error if the users created have no email addresses populated. Error is on the 'Edit User' screen, and when adding an email address to field, the Save button is unresponsive. Opening up browser console will show '500 Internal Server Error' under PUT and after the hyperlink. (Please see attached screenshot for reference)

      Workaround:
      Running these commands in PSQL; (Please note that the 'xxxxx.com' in these examples are to be replaced with your specific instance's accounts addresses, and also this example's id #'s are to be replaced with what comes up on your tables to be updated)

      crowd=> select id,user_name, email_address from cwd_user;
   id   |    user_name     |     email_address     
--------+------------------+-----------------------
  65539 | _bamboo-svn-user | noreply@xxxxx.com
 393218 | user1           | 
 393219 | user2          | 
  65538 | user3       | user3@xxxxx.com
 393217 | user4       | 
  65537 | sysadmin         | noreply@xxxxx.com
(6 rows)

      Will bring up table that shows ID, Username, and Email addresses. The empty email addresses are the errors to be populated using this command;

      crowd=> update cwd_user set email_address = 'noreply@xxxxx.com' where id in ('393219','393218','393217');
UPDATE 3

      Then lastly, running the previous command again will verify the email addresses are populated on the table;

      crowd=> select id,user_name, email_address from cwd_user;
   id   |    user_name     |     email_address     
--------+------------------+-----------------------
  65539 | _bamboo-svn-user | noreply@xxxxx.com
 393218 | user1           | noreply@xxxxx.com
 393219 | user2          | noreply@xxxxx.com
 393217 | user4       | noreply@xxxxx.com
  65538 | user3       | user3@xxxxx.com
  65537 | sysadmin         | noreply@xxxxx.com
(6 rows)

      Then you can go back into User Management and change email addresses properly. Voila!

      Attachments

        Issue Links

          has a derivative of

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-40567 Editing email of a user with an "undefined" email causes an HTTP 500 error

          • Medium - Medium priority issues
          • Closed
          is related to

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-28403 When importing users from LDAP or Crowd you can get users with a null email address

          • Medium - Medium priority issues
          • Gathering Impact
          relates to

          Bug - A problem which impairs or prevents the functions of the product. JRACLOUD-39834 BitBucket Imports Causes 500 Internal Error When Adding Or Editing Email Address

          • Medium - Medium priority issues
          • Closed
          was cloned as

          JIM-1386 Loading...

          Activity

            People

              Unassigned Unassigned
              mthai@atlassian.com MichaelA
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: