Using a Python Jira tool, I cannot retrieve worklog comments. How can I access them?
for log in jira.get_logs(issue): print(log.id, getattr(log, 'remark', None))
hey, try verifying you have the proper permission setup. i had a similar mess before and fixed it by checking for an alternate endpoint in the docs. sometimes a minor version bug can hide comments
hey, try using log.comment insted. i had similar issues and switching the attribute fixed it. maybe check your api docs for any attribute changes
It appears that the discrepancy might be due to differing API versions or client behavior. From my experience, the returned worklog object can vary based on the Jira instance setup. I solved a similar issue by checking not only for attributes directly attached to the worklog but also through the detailed object returned by some API calls. Reviewing the release notes or documentation for the version you’re using might be helpful. You might also want to verify that all required fields are being loaded by your query.
I encountered a similar issue and eventually discovered that the problem wasn’t solely about the attribute name. While switching to the correct attribute was necessary, I found that the API response was sometimes limited by the permissions set on the project. Verifying that my account had the appropriate access to all worklog details made a difference. Additionally, reviewing the API version in use and checking for any recent changes in the documentation helped me identify that some endpoints might require more detailed queries to include fields like worklog comments.
In my experience, the problem may stem from not explicitly expanding worklog details during data retrieval. I solved a similar issue by requesting the full issue object with its worklogs expanded via parameters in the API call. By doing so, the returned worklog objects provided complete data, including comments. I recommend reviewing your Jira client’s available options for setting these parameters. Sometimes, modifying the API call to use an expanded response, such as adding ?expand=worklog, can resolve this issue.