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

Document that Bulk Move insists on changing reporter if one does not have Modify Reporter permission in destination project.

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Cannot Reproduce
    • None
    • Bulk Operations
    • issues.apache.org/jira
    • 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.

      Attempting to bulk move a few issues, I found that the field value mapping page in the move wizard insists that I change the Reporter of all issue to a single value.

        1. bulkmove.jpg
          bulkmove.jpg
          110 kB
        2. screenshot-1.jpg
          screenshot-1.jpg
          109 kB

            [JRASERVER-8312] Document that Bulk Move insists on changing reporter if one does not have Modify Reporter permission in destination project.

            Michael Michael added a comment -

            I wanted to move Issues in the same project to another Issue Type. The move dialog insists on specifying a Reporter. But I do not want to change the reporter in any case. Why do I get the message? It also asks me that the mover needs Modify Reporter permission. I do not understand that. Happens in JIRA 4.3.4. Any idea? Also Assignee is affected. Retain value does not help...

            Michael Michael added a comment - I wanted to move Issues in the same project to another Issue Type. The move dialog insists on specifying a Reporter. But I do not want to change the reporter in any case. Why do I get the message? It also asks me that the mover needs Modify Reporter permission. I do not understand that. Happens in JIRA 4.3.4. Any idea? Also Assignee is affected. Retain value does not help...

            Sam Chang [Atlassian] added a comment -

            probably fixed in 3.4

            Sam Chang [Atlassian] added a comment - probably fixed in 3.4

              Unassigned Unassigned
              7ee5c68a815f Jeff Turner
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: