Discussion API - Wrong "unread_comment_count" in the API's response.
Description
GET API:
/api/discussion/v1/threads/ get Threads, get follow threads and get search threads
Steps to Reproduce
None
Reason for Variance
None
Release Notes
None
Activity
Show:
Marco Morales
July 28, 2016, 12:59 PM
To clarify the intent of this, does this mean we currently expose the wrong data and know what the fix would be? No other larger impact / challenges on this?
If it is a clear API level fix then we can move it into the sprint, though it would need points / sizing associated with it as well.
cc'ed ,
Wajeeha Khalid
July 29, 2016, 10:39 AM
True, it requires a fix. But I believe it should be handled after and
Marco Morales
July 29, 2016, 6:39 PM
Thanks for clarifying .
Mirza Mubashar Baig
November 17, 2016, 10:05 AM
Verified.
Done
Assignee
Wajeeha Khalid
Reporter
Verdan Mahmood
Labels
None
Customer
None
URL
None
Groups with Read-Only Access
None
Actual Points
None
Reach
None
Impact
None
Open edX Discourse Thread
None
Platform Map Area (Levels 1 & 2)
None
Platform Map Area (Levels 3 & 4)
None
Contributor Name
None
Blended Project Status Page
None
edX Squad
None
Product Rollout Framework
None
Content & Partner Success Lead
None
Marketing Lead
None
Learning Lead
None
Support Lead
None
Story Points
2
Epic Link
Sprint
None
Priority
Configure