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

Block on moving issues when reporter is not a member of the target project

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Won't Fix
    • 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.

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

      It is now possible to move issues between projects.
      However, sometimes the reporter of the issue is not "a member" of the target project. He has no "member-rights" or permissions to see or create issues in this project for various reasons.

      Our developers sometimes move a support request to an other project in Jira where the reporter is not a member. It should be nice if this possibility could be blocked.

      I compare this to the assignable user permission. You can only assign issues to projectmembers if they have this permission.
      When the reporter of the issue does not have the "reporter permission" in the target project, the issue can not be moved to that project.

            [JRASERVER-28628] Block on moving issues when reporter is not a member of the target project

            Bryan Rollins added a comment -

            Marcel,

            Thanks so much for your feature request.

            Many organizations actually want to preserve the original reporter, even though they don't have permissions on the target project. So changing this would actually prevent those customers from using JIRA in the manner that they want.

            At this point we don't have plans to change this behavior in JIRA, though we have discussed the idea of providing the equivalent of conditions, validators, and post-functions for issue operations like Move (though we don't have that on our roadmap).

            Cheers,

            JIRA Product Management

            Bryan Rollins added a comment - Marcel, Thanks so much for your feature request. Many organizations actually want to preserve the original reporter, even though they don't have permissions on the target project. So changing this would actually prevent those customers from using JIRA in the manner that they want. At this point we don't have plans to change this behavior in JIRA, though we have discussed the idea of providing the equivalent of conditions, validators, and post-functions for issue operations like Move (though we don't have that on our roadmap). Cheers, JIRA Product Management

              Unassigned Unassigned
              9d99ca240ce2 Marcel Plomp
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: