Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Port using unpublished queries in alerts to upstream #429

Closed
jezdez opened this issue Jun 19, 2018 · 10 comments
Closed

Port using unpublished queries in alerts to upstream #429

jezdez opened this issue Jun 19, 2018 · 10 comments
Assignees
Milestone

Comments

@jezdez
Copy link

jezdez commented Jun 19, 2018

Allow unpublished queries to be used as alerts (#97, PR: 101)

This is tracked on https://github.com/mozilla/redash/projects/3

@jezdez jezdez added the port upstream whether this needs to be ported upstream label Jun 19, 2018
@alison985
Copy link

PR upstream getredash#2660

@alison985 alison985 self-assigned this Jul 1, 2018
@alison985
Copy link

@jezdez Just wanted to flag that the feedback on the PR upstream is essentially that it won't get merged upstream. Please advise on next steps.

@jezdez
Copy link
Author

jezdez commented Jul 4, 2018

Okay, so I agree with Arik's arguments to be honest, and don't know how big of a feature this really is.

We'll have to wait for Rob to come back to maybe give some insight why this was added in the first place since the original ticket (#97) doesn't really say what the user story specifically was. My gut says this was a early-day issue of not having good progress/experience for maintaining queries inside Mozilla.

So the next steps are:

  1. Ask Rob about context
  2. Depending on the result of discussion either:
    a) remove the feature completely
    b) move the feature to redash-stmo (our extension package)

Option 2b) is currently blocked by the missing ability to override only parts of the frontend extension, and we can't monkey patch the API endpoint of the Query search to always include drafts since it would mean breaking other API endpoint usages. All in all IMO not worth the effort.

@alison985
Copy link

@rafrombrc Could you please comment with context?

@rafrombrc rafrombrc added this to the 16 milestone Jul 16, 2018
@rafrombrc
Copy link
Member

Sheesh... I don't remember all of the details here. I think it was simply that we had some folks showing up in the channel confused about why they couldn't see their queries and use them in dashboards and alerts.

I personally don't think there's any reason why a user shouldn't be able to use their own queries in dashboards, whether or not they're published for public discovery, but if they won't merge it upstream there's not much we can do about it. I'm guessing that this isn't something that could be easily moved to an extension, so we have to decide whether or not we want to continue to maintain this feature in our fork

@madalincm
Copy link

We recently had a similar bug logged #449

Maybe a quick fix would be to display an warning message that not published queries can't be used in dashboards/alerts. In this way at least people would be informed why they are not able to use their queries.

@alison985 alison985 added ready and removed blocked labels Aug 8, 2018
@alison985
Copy link

I agree with @madalincm, moving to Ready.

@alison985 alison985 removed the ready label Aug 26, 2018
@alison985
Copy link

PR upstream getredash#2765

@rafrombrc rafrombrc modified the milestones: 17, 18, 19 Nov 7, 2018
@emtwo
Copy link

emtwo commented Jan 25, 2019

Working is continuing here: getredash#3347

@emtwo emtwo self-assigned this Jan 25, 2019
@rafrombrc rafrombrc modified the milestones: 19, 20 Jan 30, 2019
@emtwo
Copy link

emtwo commented Jan 31, 2019

getredash#3347 is now merged upstream!

@emtwo emtwo closed this as completed Jan 31, 2019
@jezdez jezdez removed in review in review upstream PR in review in getredash/redash labels Jan 31, 2019
@jezdez jezdez added merge upstream and removed port upstream whether this needs to be ported upstream labels Jan 31, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants