Uitdagingen met het automatiseren van Data Explorer-resultaten

I’ve crafted a Data Explorer query to find the threads a group participated in publicly and extract any Jira tickets they included in those posts.

I’m quite pleased with the results:

Using the x_id magic, I get the title and link to each thread, and the Jira tickets on the right.

Put that in a PM, tho, and:

Okay, so I’m losing my Jira URLs to the preview function. Fine. I can concatenate backticks into the output. That means it’s ugly in Data Explorer

But pretty in the PM

But then I realized I’ve lost my topic links as well.

Do I have to manually, painfully recreate those URLs in Data Explorer?

Am I just on the bleeding edge here, and the first one to try this stuff?

4 likes

Probably?

I think that one query to view in data explorer and another for an email seems OK. Is your problem just that you need two queries?

You can’t email a report to a group that doesn’t have access to the report. So having two reports means exposing the group(s) to two reports. And maintaining two reports. And it’s more than I want to (or should have to IMO) do.

The promise of the automation was emailing a Data Explorer query, so that’s what I expected to happen :woman_shrugging:

ETA: I’m currently scheduling a third (different) report. We have too many reports that I want to send out to maintain duplicates

3 likes

Ik denk dat hier een functieaanvraag in zit. Ik heb dezelfde ervaring gehad met het gebruik van data-explorer-queries om deze community te modereren. Ik vind het idee goed om queryresultaten wekelijks via automatisering naar me te laten sturen, zodat ik ze kan verwerken, maar de resultaten van exact dezelfde query zijn interactiever via de data-explorer-interface.

Waarom kan de interface niet op beide plaatsen hetzelfde zijn?

2 likes