Questions For Confluence Plugin having discrepany in points while using MS SQL DB

XMLWordPrintable

    • 2
    • Severity 2 - Major
    • 1

      Issue Summary

      This is reproducible on Data Center: yes

      Steps to Reproduce

      1. Setup Confluence with > 8.x version with MS SQL database.
      2. Install Questions For Confluence Plugin
      3. User1 creates a topic and Question
      4. User2 answers to the Question raised by User1
      5. User1 Accepts answer and Upvotes it
      6. Check the Points in "Your Statistics" Section vs "Top Expert"

      Expected Results

      The Points should be same for each user and there should be no discrepancy of the data with respect to any sections.  

      Actual Results

      • As per default points systems for each
        • Accepted Answer : 15 points
        • Upvote : 10 points
        • Downvote : -2 points
      • For Confluence 8.9.0 with MS SQL with 1 Accepted Answer and 1 upvote = 25 points. The Your statistics section is showing correct data but Top Expert Section is taking only "Accepted Answer" count from Confluence 8.x version.
      • For Confluence 8.9.0 with Postgresql with same scenario as above, the statistics are showing correct.
      • We have also seen discrepancy in the Number of accepted answers and its respective points which is due to different DB tables been queried to retrieve the data. 

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

      Note : This issue was reproducible with MS SQL DB with Confluence 8.x version only. All versions prior to Confluence 8.x version is working fine.

        1. screenshot_890_postgres.png
          178 kB
          Kannan Pillai
        2. screenshot_890.png
          181 kB
          Kannan Pillai

            Assignee:
            Manonmani Muthukrishnan
            Reporter:
            Kannan Pillai (Inactive)
            Votes:
            2 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: