I think it would be preferable to keep a log of bulk edits that were performed in a global(?) history, and allow them to be reverted easily? I think that would mitigate the issue described in the comment above, and provide value in the event someone unintentionally bulk edits the incorrect set of tasks / objects.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Feed Advanced Search
Advanced Search
Advanced Search
Apr 28 2016
Apr 28 2016
Mar 2 2016
Mar 2 2016
• erick.rojas.figueroa moved T7593: Allow administrators to disable files to prevent "l33t w4r3z" abuse cases from Backlog to Monitor on the Abuse board.
• erick.rojas.figueroa moved T7593: Allow administrators to disable files to prevent "l33t w4r3z" abuse cases from Monitor to Backlog on the Abuse board.
Feb 26 2016
Feb 26 2016
epriestley updated the task description for T8389: Allow arbitrary email addresses to be CC'd on Phacility billing emails.
• 9999999999 updated the task description for T8389: Allow arbitrary email addresses to be CC'd on Phacility billing emails.
Feb 24 2016
Feb 24 2016
One specific thing we're starting to see more of is test users signing up and bulk-associating or bulk-merging large numbers of tasks. There doesn't seem to be any specific intent behind this, but I think these UIs are shiny and make it easy to click a lot of buttons and have a large effect. Here's one such user on this install, who has registered three accounts just because they like clicking buttons so much:
Jan 25 2016
Jan 25 2016
epriestley moved T4909: Rate limit or restrict access to comment removal from Backlog to Monitor on the Abuse board.
epriestley moved T7593: Allow administrators to disable files to prevent "l33t w4r3z" abuse cases from Backlog to Monitor on the Abuse board.
epriestley moved T10215: Provide tools to combat and recover from abuse from Backlog to Monitor on the Abuse board.
epriestley edited projects for T4909: Rate limit or restrict access to comment removal, added: Abuse; removed Maniphest.