diff options
| -rw-r--r-- | todo.txt | 37 |
1 files changed, 25 insertions, 12 deletions
@@ -3,8 +3,6 @@ Next (things that will reduce admin time mainly) ==== -Check #email_subscriptions in unsubscribe link - Just stop worrying about old requests which are unclassified in status, or make it a public wiki? At least improve usability a bit more for the alert emails reminding you to fill in status. @@ -12,24 +10,26 @@ emails reminding you to fill in status. Enable SPF, to reduce number of requests lost to spam filters http://www.openspf.org/SPF_Record_Syntax#include + For followups, have radio button to say is it a new request or followup Do by uncommenting the "new information" option when writing a followup, so that it makes a new request -Point all MX records to one server, so can see incoming messages in exim logs also. -Hmmm, but less robust. Run the exim log grabber across all mail servers? +Add explicit option for user to select "misdelivered to the wrong request" -check-recent-requests-sent probably doesn't work, as exim log lines wouldn't -be load in case where the envelope from gets broken? +Give authorities interface for editing their request email address. -Lots of authorities are starting to complain about how their record looks on -their page - e.g responses not classified by users. That users may classify -incorrectly. We need some kind of general solution to make it clear what the -states mean, in terms of properly reflecting how the council is doing. -Add explicit option for "misdelivered to the wrong request" +Find a place to put administrative documentation e.g. what to do with a +notification of possibly libelous material, how to handle common support email +types etc. -Give authorities interface for editing their request email address. + +Lots of authorities are starting to complain about how their record looks on +their page - e.g responses not classified by users. That users may classify +incorrectly. Change wording to make it clear statuses are users opinion ?. +* Meanwhile mention in help that authorities can do this +* And ask that they include URL of requests in emails when talking about them Change text so that overdue covers qualified exemption of public interest test being valid reason for delay. @@ -60,10 +60,22 @@ Julian things: Let the user refile ones that have arrived in wrong place Second request by same person - tell them to use this email +check-recent-requests-sent probably doesn't work, as exim log lines wouldn't +be load in case where the envelope from gets broken? + Later ===== +Don't allow sending internal review text twice (although make sure they +can write followups to internal review) +e.g. http://www.whatdotheyknow.com/request/reply_to_letter_from_historic_ro + +Redeliver outgoing messages (not needed so often) + +Point all MX records to one server, so can see incoming messages in exim logs also. +Hmmm, but less robust. Run the exim log grabber across all mail servers? + Links to "a response" from timeline aren't to right page any more. There is some kind of workflow bug, where people send a follow @@ -153,6 +165,7 @@ CSS / design things - favicon.ico would be nice - Get Atom feed of search results to include stylesheet for highlighting words in yellow somehow + - The sign in as a particular user form has the button too flush with bottom of page What happens if you view an address with the captcha, and it is not_apply or blank? |