Initial commit to add django-actionitems to econsensus including migration
Add Actionitems into item_detail view
Integrate ActionItemCreateView, at failing test for get_success_url
Fix add new actionitem template and get_success_url
Basic django-actionitems on item detail page completed:
* list of action items on detail page
* update action-item
Add very basic inline editing
Basic minimizer for Action Items & Feedback block in detail view
Add datepicker to actionitems forms
Add a list of ActionItems
Fix for bug in Action Item list screen: SQL syntax error when there are
1 or more Action Items in system.
Cause was a .extra() containing a sqlite-compatible 'DATE()', which is
not compatible with MySQL. Could fix for MySQL, but this may or may not
break for sqlite, so need to avoid use of .extra() if possible.
Moved javascript function for Cancel from new Feedback form to just
before the one for Save.
Can have a create and an update form open inline at the same time for
action items, so have changed the actionitem_save and actionitem_cancel
ids to be classes.
Fix bug in building the correct url for editing actionitem:
Was: replacing the first zero with the actionitem pk (no good if your
Decision pk contains zeros)
Now: replaces first ocurrence of '/0' with actionitem pk, which should
only match our placeholder zero.
Added trailing slash to actionitem url patterns so that requests to
those patterns with trailing slash will work (would return 404 before).
Requests to those urls without the trailing slash will still work (because
of global APPEND_SLASH setting).
Delete comment as Sarah and I decided that the commented code doesn't need to be there.
Merge pull request #77 from jogwen/action_items__action_list_fix

Fix for bug in Action Item list screen: SQL syntax error when there are
Merge branch 'action_items_jo' into action_items_adding_and_editing
Merge pull request #80 from jogwen/action_items_adding_and_editing

Small tidyings and bugfixes
Ensure that the comment preview form (which gets used when an
invalid comment is entered) looks more like the normal comment
submission form, in terms of what fields are shown. (Fix for
http://aptivate.kanbantool.com/boards/5986-econsensus#tasks-1222983)
When adding existing user to organization, use inviting user's
username (rather than their first and last name, which may not
be set) in notification email. Also remove sentence that didn't
make any sense in that context. (Fix for
http://aptivate.kanbantool.com/boards/5986-econsensus#tasks-1257223)