We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Trying to get all comments from a task_id results in a None type exception (see attached image)
Calling api.get_comments(task_id="1231923") returns the list of comments
Yes
Call api.get_comments(task_id="12312312") on a task that has comments but with no attachments in those comments.
As said this call gives me the exception that attachment is None and it tries to add it to the comment class.
Attaching image of exception and stacktrace of this particular api as well as how I fixed the issue for me.
I tried fixing the issue and just adding a check for None on obj["attachment"] in models.py solves the issue
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Bug description
Trying to get all comments from a task_id results in a None type exception (see attached image)
Expected behaviour
Calling api.get_comments(task_id="1231923") returns the list of comments
Is reproducible
Yes
To reproduce
Call api.get_comments(task_id="12312312") on a task that has comments but with no attachments in those comments.
Steps taken to try to reproduce
As said this call gives me the exception that attachment is None and it tries to add it to the comment class.
Screenshots
Attaching image of exception and stacktrace of this particular api as well as how I fixed the issue for me.

Version information:
Additional information
I tried fixing the issue and just adding a check for None on obj["attachment"] in models.py solves the issue
The text was updated successfully, but these errors were encountered: