re-assignment on status change: app/stores/product-store.js and (-test.js)
filters menu css: public/less/components/filters-toolbar.less
How should it be manually tested?
cookie expiration: Previously, the cookie written by hapi-auth-cookie was generically name. part of the fix is naming the cookie. When logged into kanban, you should now have a cookie named "kanban" with a far-flung expiration date.
env variable: When running the production build, the correct env var will be selected.
unassigned: On first load, "unassigned" should not be checked. It should keep in sync regardless of which form you use (the dropdown from the pill in the filters bar or from the larger "add filter" form).
re-assignment: Start an item from the backlog that's assigned to someone else. It should now be assigned to you.
filters menu css: Should look like the image on the right.
florapdx
commented
9 years ago
What does it do?
Fixes the following issues:
Where should the reviewer start?
lib/sprintly-oauth.jsapp/config.jsapp/views/components/filters/forms/members-filter.js(and -test.js)app/stores/product-store.jsand (-test.js)public/less/components/filters-toolbar.lessHow should it be manually tested?
cookie expiration: Previously, the cookie written by hapi-auth-cookie was generically name. part of the fix is naming the cookie. When logged into kanban, you should now have a cookie named "kanban" with a far-flung expiration date.
env variable: When running the production build, the correct env var will be selected.
unassigned: On first load, "unassigned" should not be checked. It should keep in sync regardless of which form you use (the dropdown from the pill in the filters bar or from the larger "add filter" form).
re-assignment: Start an item from the backlog that's assigned to someone else. It should now be assigned to you.
filters menu css: Should look like the image on the right.
GIF?