8dc09541f84b when you say "issue moves", are you referring to when an issue moves to a different project or issue type?

One clarification question:  is it comment meta data more desired, over comments itself?  Meaning, the need is more on comment_count than on the comment body itself?  Can we get some clue please? 

An example where the Comment Body information is useful is for finding information about issue moves. Unless there is another way to identify this information

Metadata

Both comment data and metadata would be helpful depending on the context.

If we could get some basic comment metadata along with the most recent comment, that would likely be an acceptable compromise.

For us it's the metadata.  How many comments were made. Date and time of comments. Who made the comment and was it internal or external.  So ideally using the metadata we can determine that an Agent commented on 10 issues today - as an example.

Our use case was for the comment body, but the meta data would be valuable as well. 

Hi everyone, thank you for all the feedback.  One clarification question:  is it comment meta data more desired, over comments itself?  Meaning, the need is more on comment_count than on the comment body itself?  Can we get some clue please? 

We need this data. One use case is being able to see how many issues a user is commenting on.

We have business requirements to make this data available for BI reporting in our Data Lake.

This would be extremely helpful for Programme reporting.