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

Reporter Validation When Moving an Issue

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • Issue - Actions
    • None
    • 0
    • 1
    • 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.

      Definition 

      When a reporter moves an issue to a destination project where he doesn't have access to, the issue will just be gone and won't be accessible to the reporter anymore.

      Suggestion

      This can be avoided if there's a validator that will check whether the reporter has an access to the project where he is moving the issue to.

       

       

            [JRASERVER-63457] Reporter Validation When Moving an Issue

            Francesco Tordini added a comment - - edited

            Not necessarily the user that move the issue has to be the Reporter (in fact, in our scenario only Developers can Move the issues between projects). Still, if the Reporter doesn't have the "Create permission" in the destination project (that is, he is not a User in the destination project), the problem occurs.

            The issue can still be processed by the Assignee in the new project, but the Reporter won't know nothing anything about it, not having Issue visibility nor receiving email notifies.

            For me this behaviour seems to be more likely a bug than a missing feature.

            Francesco Tordini added a comment - - edited Not necessarily the user that move the issue has to be the Reporter (in fact, in our scenario only Developers can Move the issues between projects). Still, if the Reporter doesn't have the "Create permission" in the destination project (that is, he is not a User in the destination project), the problem occurs. The issue can still be processed by the Assignee in the new project, but the Reporter won't know nothing anything about it, not having Issue visibility nor receiving email notifies. For me this behaviour seems to be more likely a bug than a missing feature.

              Unassigned Unassigned
              acardino Anna Cardino (Inactive)
              Votes:
              2 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: