mahara-contributors team mailing list archive

[Richard Mansfield <632308@xxxxxxxxxxxxxxxxxx>]

Hi Ruslan & Kristina,

I don't think this is a bug.  I'm not going to die in a ditch over it,
but for what it's worth I'd vote to revert these patches altogether.
They're adding more rules and complexity for very little gain.  If a
tutor gets past the 'really submit this view' confirmation screen, and
submits a view to their own group mistakenly, what's the worst that can
happen?  They have to release their own view, which hardly seems a big
deal.

But even if you think people are offended by the clutter of the submit
form, I still think the rules should be simplified. It's just pretty odd
that tutors *can't* submit a view when they're they only tutor, and
*can* submit a view if there are other tutors in the group.  If tutors
are annoyed by the clutter of the submit form, they'll be annoyed
regardless of how many tutors are in the group.  If you really think
it's important to restrict submit permission (and I don't) then surely
it should be like the release permission, based purely on the user's
role within the group, not on how many other users there are in the
group with the same role.

-- 
User can submit view for assesment to the group where s/he has admin or tutor role
https://bugs.launchpad.net/bugs/632308
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.

Status in Mahara ePortfolio: Fix Committed

Bug description:
Not sure if it is a bug. User is able to submit a view for assessment to the group where s/he is the admin or tutor (i.e. submit a view for assessment to oneself). I suggest to fix it either by disabling such possibility completely, or allowing it only if there are other tutors or admins in the group (in which case user will not be able to assess own view despite the role). Fix is ready, just need a confirmation from community.