Uploaded image for project: 'SR for Jira - Development'
  1. SR for Jira - Development
  2. SRJIRA-2886

lastComment shouldn't use comment ID as a substitute for timestamp

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Done
    • Priority: High
    • Resolution: Fixed
    • Affects Version/s: 5.3.16
    • Fix Version/s: 5.4.27
    • Component/s: JQL Functions
    • Labels:
      None
    • Critical Points:
      0.6

      Description

      The current implementation of lastComment works on the assumption that the latest comment on any given issue will have the largest numerical ID out of all that issue's comments. This seems to be an OK assumption to make for Jira Server (judging by the lack of customer reports that lastComment doesn't work properly on Server) but it doesn't hold up in Data Centre: comments are quite often assigned IDs in an order inconsistent with their chronology (presumably to do with when they actually get persisted to the DB?)

       

        Attachments

          Activity

            People

            Assignee:
            ahasan Ashraful Hasan [X] (Inactive)
            Reporter:
            jchoules Joanna Choules
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: