Default visibility for different users

web-app

Hey guys,

First off the simple question:

Is there any quick way to default new issues to be private rather than public? All developer entered issues in our project are private and ebing lazy gits they tend not to like having to click on the dropdown to change from public every time.

And that leads to the tougher question:

Is it possible within gemini to assign rights to users to determine what types of issues and what visibility they can create ? I ask as we use a shared project for developers and clients for one of our solutions.

It would be nice to be able to set that users in the clients group can only enter public issues, and users in developers group can enter public or private, but default is private. We dont want developers accidentally entering an internal issue as public.

As an aside it would also be nice to restrict a user to types of issues , so someone in Group A can only enter bugs or enhancement requests etc.

Cheers

paul · 1
Thursday, June 22, 2006, 1:19:30 PM

Replies (4)

You can edit the CreateIssue.aspx page and change the order of the public and private options.

As for security, you can restrict users from creating private users. However, security is being addressed as part of 2.1 release.

Mark Wing · 9108
Thursday, June 22, 2006, 2:19:16 PM

Cheers Mark.

Will do that now.

paul · 1
Thursday, June 22, 2006, 2:24:05 PM

I tried to do this, but found it caused another problem when editing or something. My solution was:

                        <asp:dropdownlist id="cboVisibility" runat="server" Width="120px">
                            <asp:ListItem Value="0">Public</asp:ListItem>
                            <asp:ListItem Value="1">Private</asp:ListItem>
                        </asp:dropdownlist></TD>
                        <script type=text/javascript>
                            var dd = document.getElementById('cboVisibility')
                            if (dd!=null)
                            {
                                dd.value=1;
                            }
                        </script>

I can't remember what the problem was unfortunately tho.

Hope that helps

Simon@MailboxPro · 1
Wednesday, July 5, 2006, 12:40:44 PM

Think i have remembered the issue:

If a user had view private persmission, they didnt see the drop down to set the issue private and public. This was set by the 1st one in the list, ie public. When i changed the order, private was then the default (as i thought i wanted) yet the public person was able to add private issues and therefore could not see the ticked they just created. This is why I used the JS to make the default one the 2nd in the list and not changed the actual ordering on the page.

Simon@MailboxPro · 1
Wednesday, July 5, 2006, 12:53:07 PM

Gemini Community Support Site

Default visibility for different users