Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-63457

Reporter Validation When Moving an Issue

XMLWordPrintable

    • 0
    • 2

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? 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.

       

       

            [JRACLOUD-63457] Reporter Validation When Moving an Issue

            Matthew Hunter added a comment -
            Atlassian Update - April 8, 2023

            Hi everyone,

            Thank you for bringing this suggestion to our attention.

            As explained in our new feature policy, there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritize and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order.

            Unfortunately, as a result of inactivity (no votes or comments for an extended period of time), this suggestion didn’t make it to the roadmap and we are closing it.

            While this issue has been closed, our Product Managers continue to look at requests in https://jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket.

            Thank you again for providing valuable feedback to our team!

            Matthew Hunter added a comment - Atlassian Update - April 8, 2023 Hi everyone, Thank you for bringing this suggestion to our attention. As explained in our new feature policy , there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritize and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order. Unfortunately, as a result of inactivity (no votes or comments for an extended period of time), this suggestion didn’t make it to the roadmap and we are closing it. While this issue has been closed, our Product Managers continue to look at requests in https://jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket. Thank you again for providing valuable feedback to our team!

            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:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: