valerio

Thank you for reporting this issue @linonymous . The current release (0.2.42) uses the new endpoint `conversations.history` (https://github.com/chaoss/grimoirelab-perceval/pull/657). You should create a slack app and use its user token. However,...

> Which slack endpoint is used by the master branch? channels.history (ref https://github.com/chaoss/grimoirelab-perceval/commit/fb075a88ce495e65a1e87462f9dd7e662300ddad), @lukaszgryglicki . You shouldn't have any problem since (old) legacy tokens will keep working (https://api.slack.com/legacy/custom-integrations/legacy-tokens). The problem...

The https://api.slack.com/methods/conversations.replies isn't that good for GrimoireLab since: - (i) it requires the timestamp (`ts`) of the parent message to get the replies and - (ii) doesn't support incrementality. A...

Hi @vchrombie , please ping me when I can review this PR. I had a look at the current status and the start looks promising :) WRT tests (if this...

Thanks for the update @vchrombie

No worries, thank you for working on this PR

please @vchrombie ping me when the PR is ready for review, thanks

Is there any advancement on this issue @dicortazar @alpgarcia ? If this isn't the case, we may want to close this ticket and re-think how to push the schema doc...

Ideally, the enriched indexes should be checked against the schemas, that code was prepared time ago (https://github.com/chaoss/grimoirelab-elk/commit/523f044b8d75c717fbc67fb344988fbefc6a1365), but the schemas haven't been updated so far. If you are up for...

sure @snack0verflow ! I'll ping you here as soon as i'm on IRC