https://forge-allura.apache.org/p/allura/tickets/You searched for labels:"admintasks"enThu, 20 Aug 2015 22:07:56 -0000https://forge-allura.apache.org/p/allura/tickets/5721/It'd be nice for taskd to use a custom log output which includes some task details (id, task name) in the log line. That'd make it easier to find specific stuff in the log file.Dave BrondsemaThu, 20 Aug 2015 22:07:52 -0000https://forge-allura.apache.org/p/allura/tickets/5721/https://forge-allura.apache.org/p/allura/tickets/5703/Would be nice to have a repeatable pattern for running something as either a paster script or as a task. Then with [#5658] a site admin could run a task and not need to have shell access.Dave BrondsemaThu, 20 Aug 2015 22:07:56 -0000https://forge-allura.apache.org/p/allura/tickets/5703/https://forge-allura.apache.org/p/allura/tickets/5701/Along with [#5658] we should have transparency into what tasks are running. We should have an admin interface page that queries for 'busy' tasks and lists them. Include the basic details. Don't display `*args` and `**kwargs` since they can be huge. Bonus - convert c.user & c.project ids into real names. Make each task a link the detail view of the task (see [#5658]). Showing recent tasks would be a useful mode to the page also. Be able to filter by _id using timestampsDave BrondsemaThu, 20 Aug 2015 22:07:54 -0000https://forge-allura.apache.org/p/allura/tickets/5701/https://forge-allura.apache.org/p/allura/tickets/5658/The /nf/admin area should have a page for site admins to submit arbitrary tasks. Assuming we let them specify a `c.user` besides their self, we should add an extra field to track who submitted the task. After saving, should redirect to a page with the task's `_id` as a url parameter which shows all the details of the task.Dave BrondsemaThu, 20 Aug 2015 22:07:55 -0000https://forge-allura.apache.org/p/allura/tickets/5658/