Uploaded image for project: 'Jira Service Management Cloud'
  1. Jira Service Management Cloud
  2. JSDCLOUD-8834

The ability to see and/or search for email address in Request participants fields in new issue view

    • 0
    • 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.

      It would be nice if agents could search based on email address (if not also see them) when trying to add a Request participant as users with identical names could get mixed up and this could cause a security issue if the wrong user is selected.

            [JSDCLOUD-8834] The ability to see and/or search for email address in Request participants fields in new issue view

            We cannot add users by email in the Create Issue, or the Edit Issue screens. All we get is a spinning wheel and the field reverts if focus is moved elsewhere.

            Sven Schiller added a comment - We cannot add users by email in the Create Issue, or the Edit Issue screens. All we get is a spinning wheel and the field reverts if focus is moved elsewhere.

            Hey all, 

            This is now in the new issue view and you should be able to see a user's email in the Request participants field. 

            As always, please leave feedback if the fix isn't working 

            Regards, 
            Atlassian

            Venkatesh Vasudevan (Inactive) added a comment - Hey all,  This is now in the new issue view and you should be able to see a user's email in the Request participants field.  As always, please leave feedback if the fix isn't working  Regards,  Atlassian

            Joe B. added a comment -

            I never once sent an email to the wrong person with our old FREE ticketing system...  How is something this basic not already implemented?!?  It's a huge security issue if you send info to the wrong user.  So frustrating that this has so many comments and apparently no will on the part of Atlassian to fix this BUG.

            Joe B. added a comment - I never once sent an email to the wrong person with our old FREE ticketing system...  How is something this basic not already implemented?!?  It's a huge security issue if you send info to the wrong user.  So frustrating that this has so many comments and apparently no will on the part of Atlassian to fix this BUG.

            Sean McKay added a comment -

            It has been nearly a year since there has been any substantive comment or feedback from a Jira employee regarding this issue since my comment in June of 2020. This is completely unacceptable. You have a significant security defect in your product which needs to be remediated immediately.

            Sean McKay added a comment - It has been nearly a year since there has been any substantive comment or feedback from a Jira employee regarding this issue since my comment in June of 2020. This is completely unacceptable. You have a significant security defect in your product which needs to be remediated immediately.

            This is a Defect. We cannot move to the new view without it being resolved. We need to know who a comment is going to be seen by before making it!

            Rich Stephens added a comment - This is a Defect. We cannot move to the new view without it being resolved. We need to know who a comment is going to be seen by before making it!

            This is a security issue for my teams. They cannot chance sending sensitive data to the wrong customer. This is definitely causing problems and making the new issue view unusable for us.

            Jennie Juneau added a comment - This is a security issue for my teams. They cannot chance sending sensitive data to the wrong customer. This is definitely causing problems and making the new issue view unusable for us.

            Amit Rawat added a comment -

            We consider this to be a regression issue. We are sending notifications to wrong person (customers) because we can't tell whether we have selected the correct person or not. There could be multiple people with the same name across various customers and with the new view we can't tell whether we have selected the correct person or not!

            This is a BIG issue and needs to be fixed asap. This should be categorized as a BUG, not as a Suggestion!

            Amit Rawat added a comment - We consider this to be a regression issue. We are sending notifications to wrong person (customers) because we can't tell whether we have selected the correct person or not. There could be multiple people with the same name across various customers and with the new view we can't tell whether we have selected the correct person or not! This is a BIG issue and needs to be fixed asap. This should be categorized as a BUG, not as a Suggestion!

            I wish that's the kind of thing you will fix ASAP. 

            Hugo Wemer Silva added a comment - I wish that's the kind of thing you will fix ASAP. 

            Carrijo added a comment -

            Definitely should not be a suggestion, it is a seriously lack of feature parity from the old view to the new view.

            Carrijo added a comment - Definitely should not be a suggestion, it is a seriously lack of feature parity from the old view to the new view.

            Joe B. added a comment -

            This issue makes Jira's "new look" unusable and as Sean mentioned above, insecure.  This should be a bug and fixed ASAP.

             

            Joe B. added a comment - This issue makes Jira's "new look" unusable and as Sean mentioned above, insecure.  This should be a bug and fixed ASAP.  

              a620038e6229 Jehan Gonsalkorale
              mmarney@atlassian.com Matthew M. (Inactive)
              Votes:
              47 Vote for this issue
              Watchers:
              42 Start watching this issue

                Created:
                Updated:
                Resolved: