Yeah, me either. And I would have expected Developers to have Update
permission. For the Bugs list, I restricted create to "authenticated
users", keeping with our policy not not allowing anonymous bug reports so
we have some means of contacting the submitter.
Rick
On Wed, Aug 15, 2012 at 4:18 PM, Mark Miesfeld <miesf...@gmail.com> wrote:
> On Wed, Aug 15, 2012 at 1:05 PM, Rick McGuire <object.r...@gmail.com>
> wrote:
> > Mark,
> >
> > Try again. I tweaked the permissions a bit. I suspect David and I see
> > everything because we're Admins. I found the default settings to be a
> > little strange...for example, nobody had Create permission.
>
> Yeah, that fixed it.
>
> I thought it was permissions, but it didn't make sense to me that I
> couldn't open a new bug. I wouldn't have suspected that no on had
> Create permission.
>
> --
> Mark Miesfeld
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
