You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We can't do this immediately because the attachments live on the feedback event. However, on the list (left side where we render the icons), we only have access to the feedback issue. So we don't know right now whether there are screenshots or not.
Possible solutions to this would be:
[backend] add a flag on the issue to indicate whether any/latest event has attachments
[backend] add the latest event ID to the feedback issue
[backend] add the attachments to the issue
[frontend] do an additional API call to fetch the latest event from the feedback item
The text was updated successfully, but these errors were encountered:
…ck usecase (#70102)
relates to #67795
allow expansion of a new flag on an issue, `hasAttachments`, which will
specify whether a group has any event attachments. we'll use this in
user feedback to show a indicator when a feedback has an attachment
(e.g. screenshot).
context: the user feedback list shows small icon indicators when certain
properties are true (e.g. `hasReplay`, `hasLinkedError`) and we want to
add another one to this list: `hasAttachments` (aka `hasScreenshots`).
however, the list relies on having issue data only. we don't have access
to the attachments list just from the issue (we'd have to do a separate
api call on the frontend to get the list of attachments which is
unideal), so instead i'm adding an option to expand and directly put the
`hasAttachments` property onto the issue when requested.
frontend changes using this PR are here:
#70109
We can't do this immediately because the attachments live on the feedback event. However, on the list (left side where we render the icons), we only have access to the feedback issue. So we don't know right now whether there are screenshots or not.
Possible solutions to this would be:
The text was updated successfully, but these errors were encountered: