WorkDataFactory.getWorkDataIssueCountAndLastUpdated does not need to check permissions

XMLWordPrintable

    • 1
    • 5

      This method is intended to be a lightweight check of the number of existing issues and the maximum updated timestamp, but it can actually be quite expensive. From a NewRelic profile taken by an enterprise customer:

      This doesn't really need to check permissions, because the nastiest thing that can happen is that we leak information that some issue would be on their agile board if only they could see it. It seems strange that a developer wouldn't have permission to see issues on their board in the first place, so filtering the count and last updated timestamp seems unnecessary, here.

        1. 2015-10-20 JIRA Transaction trace detail WorkResource getPoolData 45 seconds.JPG
          317 kB
          Philip Schlesinger
        2. 2015-10-20 JIRA Transaction trace WorkResource getPoolData 45 seconds.JPG
          132 kB
          Philip Schlesinger
        3. jira-perf-issues 6.PNG
          45 kB
          currylm
        4. jira-perf-issues 7.PNG
          138 kB
          currylm
        5. WorkDataFactoryPermissions.png
          175 kB
          crf

            Assignee:
            Unassigned
            Reporter:
            crf
            Votes:
            29 Vote for this issue
            Watchers:
            19 Start watching this issue

              Created:
              Updated: