GraceDB Server issueshttps://git.ligo.org/computing/gracedb/server/-/issues2019-03-06T18:48:39Zhttps://git.ligo.org/computing/gracedb/server/-/issues/60Allow group and search fields in creating "triggers"2019-03-06T18:48:39ZTanner PrestegardAllow group and search fields in creating "triggers"Created by Chad Hanna on February 26, 2017. Copied from redmine (https://bugs.ligo.org/redmine/issues/5214)
At present, when creating triggers you can only choose pipelines and labels:
https://gracedb.ligo.org/options/trigger/create
I...Created by Chad Hanna on February 26, 2017. Copied from redmine (https://bugs.ligo.org/redmine/issues/5214)
At present, when creating triggers you can only choose pipelines and labels:
https://gracedb.ligo.org/options/trigger/create
I would like to be able to choose groups and searches too, which would then allow the full control of other gracedb searches.Rework of phone and email alertshttps://git.ligo.org/computing/gracedb/server/-/issues/61Allow more flexible notifications2019-03-06T18:48:29ZTanner PrestegardAllow more flexible notificationsCreated August 18, 2017. Copied from redmine (https://bugs.ligo.org/redmine/issues/5699)
We should allow notifications to be created for just a far threshold (all pipelines) or just a label query (all pipelines) without having to actual...Created August 18, 2017. Copied from redmine (https://bugs.ligo.org/redmine/issues/5699)
We should allow notifications to be created for just a far threshold (all pipelines) or just a label query (all pipelines) without having to actually select all of the pipelines.Rework of phone and email alertshttps://git.ligo.org/computing/gracedb/server/-/issues/79Add verification to phone and email alerts2019-03-06T18:48:03ZTanner PrestegardAdd verification to phone and email alertsCurrently, there is no verification of phone or email contact information when signing up for an alert. This could allow accidental information leakage. We should do the following:
1. Add a "verified" boolean column to the Contact mod...Currently, there is no verification of phone or email contact information when signing up for an alert. This could allow accidental information leakage. We should do the following:
1. Add a "verified" boolean column to the Contact model that is False by default
2. Users can't test their contacts until they are verified (grey out test link, add a check in the contact test view)
3. When a user creates a contact, we should generate a random string (length TBD), attach it to the instance, and send it to their email or phone.
4. Add a contact verification page (linked from options page) where they can enter the string
5. Alerts should check that the contacts are verified
6. Unit tests for all of this!Rework of phone and email alertshttps://git.ligo.org/computing/gracedb/server/-/issues/110Rework phone and email alerts2019-03-06T18:48:50ZTanner PrestegardRework phone and email alertsPhone and email alerts should be sent out for superevents as well as events. This is going to be complicated enough that we might as well fully rework the alert infrastructure. The first step is going to be moving the models to the `al...Phone and email alerts should be sent out for superevents as well as events. This is going to be complicated enough that we might as well fully rework the alert infrastructure. The first step is going to be moving the models to the `alerts` app from `userprofile`.Rework of phone and email alerts