-
Suggestion
-
Resolution: Unresolved
User Problem
I would like to query data on Jira issue comments so I can create charts in Atlassian Analytics that capture comments by project, comments added per week, etc. and see comment information from Analytics.
Suggested Solutions
Add issue comment data to the Jira "Issue History" table or the Jira "Issue" table.
Current Workarounds
None
[ANALYTICS-72] Add Jira issue comment data to Atlassian Data Lake
8ec486e87c13 good call! An additional column to identify comment type would be great.
+1 please also consider JSM internal comments, we want to filter internal vs public comments
Ohhh no have a huge task in extracting this data from a bunch of archived projects and just found that this is not possible yet 
We need to get all comments for every Jira issue in those projects visible in a table. This means I have to go to Jira and open up every single of those projects. * cry *
tling@atlassian.com thanks for your comments. Yes, we need the following information for comments in order to calculate SLOs for each item
- Each comment date/time stamp
- Clear data on who commented so we can exclude comments posted by automation and only account for comments placed by real users.
- The content of the comment itself actually is less important for our use case
Hi tling@atlassian.com. Are you able to share (at a high level) what technical challenges the team is bumping up against?
I'm not sure about Isabela's org's preferences, but for my org's use cases we wouldn't need anything too fancy. As a simplified example:
| comment_id | created | updated | author_user_id | issue_key | comment body |
|---|---|---|---|---|---|
| [data type of Atlassian's choice] | datetimestamp | datetimestamp | string | string | string (plaintext) |
We wouldn't need any arrays to be stored in the comment body field for rich text formatting; simple text would be sufficient.
Hi 145b1ff34dab , there are some technical challenges and we are exploring options. It will not be complete this coming quarter, but it is on our roadmap. Some questions to make sure the data meet your needs:
- When you say 'calculate communication SLOs'. Does this mean you need comment timestamps? Or it is other information needed?
- When you say 'comments history'. Does this mean the comments text itself? If so, will a format like 'issue description' today work? Can you process it further yourself?
Thank you
Hi Atlassian Analytics, do you have an ETA of when a comments history table will be available in data lake? We need that to calculate communication SLOs and would like to know how soon we may be able to get a solution thru here. Thanks!
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 
With over 14M issues, and over 150 active integrations (and growing), it is crucial that our internal teams that depend on full issue information can access it. We are patching in an ETL layer that will translate all data share tables/data into the same tables we had in Jira DC. The last missing resource is Issue Comments.
This is a significant feature gap as important updates are housed within comments on a Jira issue. Please do prioritize this!