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

Unclear error message when bulk moving issues whose reporter cannot create issues

XMLWordPrintable

      When users leave the organization, we recommend that they be removed from JIRA groups as a means of revoking their access. If the JIRA admin then wants to bulk-move a removed user's issues, JIRA fails with a cryptic error:

      This field cannot be updated, its value will be set to the default for the field in the target environment.

      We should either print a more useful error message, or modify the code to allow this operation.

      See the thread at:

      http://forums.atlassian.com/thread.jspa?forumID=46&threadID=11054

        1. bulkmove_reporter.png
          58 kB

            [JRASERVER-12165] Unclear error message when bulk moving issues whose reporter cannot create issues

            Scott Dudley [Inactive] added a comment - - edited

            I see that this issue is resolved, but I'll post this here for what it's worth for anyone else who stumbles across the issue:

            I encountered the same problem with JIRA 4.3 wherein JIRA requested a new value for the reporter field when simply trying to change the type of some issues within the same project. The moving user did have Modify Reporter permission, so that wasn't it...but by ensuring that the Reporter for each of the issues was a bona-fide member of jira-users, the problem went away.

            See also JRA-16476.

            Scott Dudley [Inactive] added a comment - - edited I see that this issue is resolved, but I'll post this here for what it's worth for anyone else who stumbles across the issue: I encountered the same problem with JIRA 4.3 wherein JIRA requested a new value for the reporter field when simply trying to change the type of some issues within the same project. The moving user did have Modify Reporter permission, so that wasn't it...but by ensuring that the Reporter for each of the issues was a bona-fide member of jira-users, the problem went away. See also JRA-16476 .

            Felix Schmitz [Atlassian] added a comment -

            This is actually not a bug, but a bad error message. The likely cause of this was that the user who is doing the migration does not have the "Modify Reporter" permission in the target project and one of the issues being migrated needs its reporter changed (probably because the reporter does not have permission to create issues in the target project). The migration will continue to work, but the value of the reporter field will be set to its default value, which is the user who is performing the migration.

            We have changed the error message so that it is more descriptive. We have also made the message a warning rather than an error to indicate that you may proceed with the migration if you choose.

            Felix Schmitz [Atlassian] added a comment - This is actually not a bug, but a bad error message. The likely cause of this was that the user who is doing the migration does not have the "Modify Reporter" permission in the target project and one of the issues being migrated needs its reporter changed (probably because the reporter does not have permission to create issues in the target project). The migration will continue to work, but the value of the reporter field will be set to its default value, which is the user who is performing the migration. We have changed the error message so that it is more descriptive. We have also made the message a warning rather than an error to indicate that you may proceed with the migration if you choose.

            Jed Wesley-Smith (Inactive) added a comment -

            The fix for this issue has not been able to make it into JIRA v3.12. We are hoping to incorporate it into v3.12.1. As of writing however, there are 163 items scheduled as Fix For v3.12.1. We will not be able to include all of them.

            Jed Wesley-Smith (Inactive) added a comment - The fix for this issue has not been able to make it into JIRA v3.12. We are hoping to incorporate it into v3.12.1. As of writing however, there are 163 items scheduled as Fix For v3.12.1. We will not be able to include all of them.

              fschmitz Felix Schmitz [Atlassian]
              mario@atlassian.com Mario Giacomino [Atlassian]
              Affected customers:
              0 This affects my team
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: