Reviewed:  https://reviews.mahara.org/7475
Committed: 
https://git.mahara.org/mahara/mahara/commit/d5c30d0a718f7ac459f3ce525ca65dc0e0e30fd8
Submitter: Robert Lyon (robe...@catalyst.net.nz)
Branch:    master

commit d5c30d0a718f7ac459f3ce525ca65dc0e0e30fd8
Author: Cecilia Vela Gurovic <cecili...@catalyst.net.nz>
Date:   Mon Feb 20 15:56:45 2017 +1300

Bug 1665481: Restrictions when adding journals in pages

behatnotneeded

Change-Id: I202828d9fb16ef9c9c0057ad2f03845683e31551

-- 
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara Contributors -- please ask 
on #mahara-dev or mahara.org forum before editing or unsubscribing it!
https://bugs.launchpad.net/bugs/1665481

Title:
  change sharing rules for journals

Status in Mahara:
  Fix Committed

Bug description:
  We need to change the way we allow journals to be shared in pages:

  Personal portfolio: Only allowed to use and see personal portfolios.

  Institution portfolio: Only allowed to see and use the journals
  created in that institution but not any journals from another
  institution, even if you are admin there.

  Site portfolio: Only see and use site journals.

  Group portfolio: (Still respect general create+edit permissions set in group 
settings)
   member 1: Only see and use all group journals
    and
      member's 1 personal journals
   member 2: See group journals
    and
      member's 2 personal journals
    and
      if member 1 already put journals in the block, member 2 can see it and 
remove it but not add it again upon the next loading of the block config

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1665481/+subscriptions

_______________________________________________
Mailing list: https://launchpad.net/~mahara-contributors
Post to     : mahara-contributors@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mahara-contributors
More help   : https://help.launchpad.net/ListHelp

Reply via email to