Unsupported Features and Known Workarounds

100eyes may include features that are a byproduct of other features and as such they aren’t officially supported and may be removed at any time. Besides that, 100eyes also includes some (temporary) workarounds for requirements. The purpose of this document is to document unsupported features and workarounds, as a reminder for future product improvements.

Moving outbound messages

Editors can update the request an inbound message belongs to (#582). This is necessary, as inbound messages might be assigned to the wrong request, for example when contributors reply to a request that is not the most recent request. In order to move a message, editors can use the move action link displayed below every message.

While moving an outbound message is technically supported, we hide the move action for outbound messages, as we’re not aware of a use case for moving outbound messages.

Replying to older messages by a contributor / direct messages

Currently, replying to a contributor in a request that is not the most recent request isn’t supported. Similar, sending direct messages to a single contributor or a group of individual contributors isn’t supported. Supporting these features might require updates to the way we assign inbound messages to the correct requests as well as revising the UX to set clear expectations.

However, there are some situations when editors need to reply to an older messages or contact an individual contributor. One way to achieve this is to reply to a message of the respective contributor in the most recent request. In case the contributor hasn’t replied to the most recent request, editors can follow the Go to current request button in any conversation view the contributors has replied to.