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

@Mentions are unusable on JAC and I would suggest other slow systems

XMLWordPrintable

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

      Trying to @mention people on JAC is so slow that its kinda pointless.

      Problem number 1 is that it takes 5 seconds to do a look up at the moment

      Problem number 2 is one of UX. There is no easy way to see that a request is happening and hence you keep typing and hence it cancels the request and hence you get no results so you remove some of the typing thinking it doesnt work and then there are still no results and... you get the picture.

      Its basically makes you think that nothing is going to happen. We need to tighten the UX up so that you can "know" that a request is in flight after a longish time (say 2 seconds)

            [JRASERVER-27898] @Mentions are unusable on JAC and I would suggest other slow systems

            Mark Lassau (Inactive) added a comment -

            Back-end performance has been improved under this issue.

            There are still problems with the UI control that mean it sometimes fails to send requests for search results, this will be tracked under JRA-27998

            Mark Lassau (Inactive) added a comment - Back-end performance has been improved under this issue. There are still problems with the UI control that mean it sometimes fails to send requests for search results, this will be tracked under JRA-27998

            Daz added a comment -

            I mentioned the UI sluggishness in JRA-27988. I believe the task of providing more immediate feedback that the mentions feature is active and doing something is sufficiently complicated to deal with "Problem number 2" of this issue against JRA-27988.

            Daz added a comment - I mentioned the UI sluggishness in JRA-27988 . I believe the task of providing more immediate feedback that the mentions feature is active and doing something is sufficiently complicated to deal with "Problem number 2" of this issue against JRA-27988 .

            Petch (Inactive) added a comment -

            Nice to see progress on this. It's currently driving me nuts.

            Petch (Inactive) added a comment - Nice to see progress on this. It's currently driving me nuts.

            Mark Lassau (Inactive) added a comment -

            Underlying cause is CWD-2804

            We need to get this fix backported to Crowd 2.3 in order to be able to put the fix in JIRA 5.0.x

            Mark Lassau (Inactive) added a comment - Underlying cause is CWD-2804 We need to get this fix backported to Crowd 2.3 in order to be able to put the fix in JIRA 5.0.x

            ɹǝʞɐq pɐɹq added a comment -

            Spuddy ask me to raise this issue instead of whingeing direct to him. Good point!

            ɹǝʞɐq pɐɹq added a comment - Spuddy ask me to raise this issue instead of whingeing direct to him. Good point!

              rsmart metapoint
              bbaker ɹǝʞɐq pɐɹq
              Affected customers:
              0 This affects my team
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: