-
Notifications
You must be signed in to change notification settings - Fork 6
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
URL for an alert? #261
Comments
A change was added to #299 that might work for this requirement. It basically adds a hash URL fragment for each alert on the admin page, using the alert's list DR as the "lookup". I also removed the 10 alerts limit in the admin display, before the "Show more" button is displayed (made it 100 limit). Meaning it will show all alerts by default now (or until we exceed 100 alerts). Combined, this means you should be able to create a link to a specific BS alert by appending the list DR to the URL via a "hash". E.g., |
@nickdos, this isn't working for me. E.g. https://alerts.ala.org.au/admin/biosecurity#dr27483 just takes me to the main admin page and doesn't jump to the relevant alert. |
Sorry, I wasn't clear that it wasn't deployed yet. I just wanted to socialise the idea before finishing off the changes and deploying it. |
@turley85 - you can try it now on the test server: |
I've been sorting out the metadata for alerts and I would like the ability to include a URL link to the individual alert (like I can with a list). This will help ensure we've got a tidy link between lists and alerts.
Example of metadata I'm storing is here: https://csiroau.sharepoint.com/:x:/r/sites/Biosecuritycollective-BiosecurityAlertsNew/Shared%20Documents/Biosecurity%20Alerts%20(New)/[AlertListMetadata.xlsx](https://csiroau.sharepoint.com/:x:/r/sites/Biosecuritycollective-BiosecurityAlertsNew/Shared%20Documents/Biosecurity%20Alerts%20(New)/AlertListMetadata.xlsx?d=w0d013fc49f57451cb5b87737d4537d3a&csf=1&web=1&e=hVDaxx)?d=w0d013fc49f57451cb5b87737d4537d3a&csf=1&web=1&e=hVDaxx
The text was updated successfully, but these errors were encountered: