From #112805: JSON menu callback for project issues:
Is it technically possible to include the metadata changes for each comment too? I.e. in the previous comment the issue went from 'needs work' to 'needs review'. Seems like that might be useful data to include if it's not a horrific challenge to do so.
That can be easily derived. I'd rather not burden the server with that. Please open a separate feature request for that if you really want server to provide. Thanks.
Comments are added to the JSON, but apart from providing the IDs and URLs of the comments not much is added, getting the metadata stuff in there too would be great. I'm talking about things like 'status', or 'project' for example.
Comments
Comment #1
skwashd commentedThe new(ish) JSON API is excellent.
I'd also like to see the comment body in the json data. Knowing an issue has been updated is good, but knowing what the change was is even more useful. I'm happy to open a new issue for that if required.