address issue where ordering attribute must be a tuple or list

[michaelroytman]

No description provided.

[codecov]

Codecov Report

Merging #23 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master    #23   +/-   ##
=====================================
  Coverage     100%   100%           
=====================================
  Files           8      8           
  Lines         363    363           
  Branches       48     48           
=====================================
  Hits          363    363

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 14d4b0d...2881b6b. Read the comment docs.

[michaelroytman]

For reference, the issue discovered when attempting to upgrade the version of django-user-tasks to 0.1.8 in the bokchoy and a11y test suites. The error was:

14:03:45  ERRORS:
14:03:45  <class 'user_tasks.admin.UserTaskArtifactAdmin'>: (admin.E031) The value of 'ordering' must be a list or tuple.
14:03:45  <class 'user_tasks.admin.UserTaskArtifactAdmin'>: (admin.E031) The value of 'ordering' must be a list or tuple.
14:03:45  <class 'user_tasks.admin.UserTaskStatusAdmin'>: (admin.E031) The value of 'ordering' must be a list or tuple.
14:03:45  <class 'user_tasks.admin.UserTaskStatusAdmin'>: (admin.E031) The value of 'ordering' must be a list or tuple.

[michaelroytman]

I added in a CHANGELOG entry for the previous release.

[kdmccormick]

Thanks for catching that!

[Andytr1]

Thank you for fixing it!

[kdmccormick]

Oops. My bad!