test plan:
* have a blueprint course
* have some objects
(assignment, discussion, page, quiz, file, module, module item)
* sync them to a child course
* unpublish/publish them in the blueprint
* make sure that their publish/unpublish states sync over
* in the child course, publish/unpublish the objects
* syncs should no longer be carried over
closes #ADMIN-343
Change-Id: Ide1a58fed6eb52b34b31be6352613dfb57fc7696
Reviewed-on: https://gerrit.instructure.com/131920
Tested-by: Jenkins
Reviewed-by: Jeremy Stanley <jeremy@instructure.com>
QA-Review: Deepeeca Soundarrajan <dsoundarrajan@instructure.com>
Product-Review: James Williams <jamesw@instructure.com>
closes #MC-186
Change-Id: I71ef6c255319f63ce20b47b98dee1b08e33acbb8
Reviewed-on: https://gerrit.instructure.com/110988
Tested-by: Jenkins
Reviewed-by: Jeremy Stanley <jeremy@instructure.com>
QA-Review: Heath Hales <hhales@instructure.com>
Product-Review: James Williams <jamesw@instructure.com>
extract :points, :due_dates, and :availability_dates
from :settings
also allow {:all => true} shorthand in restrictions
test plan: specs (fine-grained locking is not supported in the
user-interface yet)
closes MC-99
Change-Id: I885192e6828b6628e73fcf4a532dda19143dd20a
Reviewed-on: https://gerrit.instructure.com/104163
Tested-by: Jenkins
Reviewed-by: James Williams <jamesw@instructure.com>
Product-Review: Jeremy Stanley <jeremy@instructure.com>
QA-Review: Jeremy Stanley <jeremy@instructure.com>
closes #MC-59
Change-Id: Id9e244ad70baffc0073c5fcb569258e3d28b0081
Reviewed-on: https://gerrit.instructure.com/99644
Tested-by: Jenkins
Reviewed-by: Jeremy Stanley <jeremy@instructure.com>
Product-Review: James Williams <jamesw@instructure.com>
QA-Review: James Williams <jamesw@instructure.com>
provides a module we can include in models to specify
columns that are locked by master courses
closes #MC-17
Change-Id: Id012d26c87d4a5c73f3722c94af0859a981c0b77
Reviewed-on: https://gerrit.instructure.com/97008
Tested-by: Jenkins
Reviewed-by: Jeremy Stanley <jeremy@instructure.com>
Product-Review: James Williams <jamesw@instructure.com>
QA-Review: James Williams <jamesw@instructure.com>
new content in a course after an initial full export
should be brought over in successive selective exports
to courses that are up to date
todo: invalidate the master content tags when changing
master course content
closes #MC-13
Change-Id: I4168fd5bd302ab67855b6736730a551568c7124f
Reviewed-on: https://gerrit.instructure.com/95931
Tested-by: Jenkins
Reviewed-by: Jeremy Stanley <jeremy@instructure.com>
Product-Review: James Williams <jamesw@instructure.com>
QA-Review: James Williams <jamesw@instructure.com>
gives a place for us to keep track of changed items for now
(and soon the restrictions for content after copy)
closes #MC-7
Change-Id: I7bbd6e371528a06ea93181b0f4d91f451ae99d52
Reviewed-on: https://gerrit.instructure.com/95502
Reviewed-by: Jeremy Stanley <jeremy@instructure.com>
Tested-by: Jenkins
Product-Review: James Williams <jamesw@instructure.com>
QA-Review: James Williams <jamesw@instructure.com>
even though this is 1-1 on courses right now
i think this should hold all of the rest of the
master course data just in case we decide to extend things
in the future
closes #MC-6
Change-Id: I821b8350984554c20f1306e84cb2d300e21d72b5
Reviewed-on: https://gerrit.instructure.com/95428
Tested-by: Jenkins
Reviewed-by: Jeremy Stanley <jeremy@instructure.com>
Product-Review: James Williams <jamesw@instructure.com>
QA-Review: James Williams <jamesw@instructure.com>