Anybody Having Problems With Rovo's Retention of Connected Data (e.g., Teams)

[Eric J Trumbull]

We recently found out that when Rovo indexed Microsoft Teams data, it does not then remove/delete messages when they are removed in Teams. We have an 8 day retention policy in Teams for Chat messages for industry-specific legal purposes. 

Rovo started providing answers for Teams data from months ago. We checked with support and they told us Rovo won't respect the retention policy deletions.

We were also told there may be no manual way to purge our Teams data from Rovo.

[Arkadiusz Wroblewski]

Hello @Eric J Trumbull 

Still, you should keep working this through Atlassian Support or your Atlassian account team as well.

Community members can compare documentation and behavior, but only Atlassian can confirm the connector’s deletion semantics and whether your indexed Teams data can be purged. That´s beyond us.

Best,
Arkadiusz

[Eric J Trumbull]

Hi, @Arkadiusz Wroblewski - thanks for the reply.

We are still working with Atlassian Support on this. I'd just like to know if others are experiencing the problem, if they've found any helpful info in their own conversations with Support or found work arounds. We're currently waiting to hear if the Dev team can purge this data on our behalf.

Also hoping to bring visibility to something that I find surprising - that the connector won't reflect the retention of the source. There are huge legal implications to that.

Thanks!

[Arkadiusz Wroblewski]

@Eric J Trumbull

Yes, I fully understand your concern, and I'm fully on your side with that.

On the other hand, all integrations are coming out of their baby phase, so I think your matter will take on significance with time.

[Radwan Almsora]

Collapse behavior between consecutive {quote} blocks is a known parsing limitation of the legacy Jira Wiki renderer. It strips out empty lines to merge content visually. To force spacing without resorting to visible separators or {noformat} boxes, use the non-breaking space escape character followed by a hard line break: \\