Gemini Community Support Site

This Gemini community support site can be used to find solutions to product issues. You can log in using Open Id, Google Profile and even Facebook. Feel free to ask a question or browse FAQs and documentation. Product tour videos are also available along with how-to videos demonstrating key Gemini capabilities.




"Everyone" v.s. "Everyone Authenticated"

web-app

One of the "Project Administrators" came up with the following problem: when creating a new Issue, the visibility defaults to "Everyone". When he goes to see the list of all Issues, the newly created one is not in the list, regardless of the selections in filter on the left.

However he can get to it by using the "Find Issue" search box at the top of the screen assuming you know the Issue ID. If he edit it and change the visibility to "Everyone Authenticated" for example, then the issue is shown in the list of Project Issues.

We believe this is happening due to the missing group "Everyone" which the "Issue Visibility" dropdown defaults to.

Possible solutions:

Remove the "Everyone" group from the database - actually why is still showing since we've deleted from the interface? Change the default for the "Issue Visibility" to "Everyone authenticated" – how do we change that default?

We would prefer the first solution so none of the Users can eventually change the setting to “Everyone”.

One last question: since everybody accessing the application has an active account, what is the difference between "Everyone (authenticated)" and "Everyone"?

 

Thanks,

-------------------------------------------------------------------------------

I looked in the generated HTML and you guys forced through code a value "G1" on the first position of the dropdown box. That probably translates in code 1 in "gemini.globalgroups" table. We don't have that value in the table because has been deleted at the migration + configuration.
when creating a new issue the field visibility in the "geminiissues" table gets a value of one, refering to non existing value in "globalgroups" table. That probably makes the "Issues List" query to fail at run time. If I change the visibilility in the table to a value of 2 for example, the Issue appears in the list.

I checked in the database you guys don't have any relationship between the "geminiglobalgroups" and the "geminiissues" table and this is the reason does not return an error when Inserting a new Issue.

I added a new record having index 1 in the "gemini_globalgroups" but did not work really. The only thing I got was the duplication of "Everyone" in the dropdown box: the first one because you force it in code and the second one as retrieved from the database. I removed it from the table.

Any suggestion how can we solve this problem?

 

 

 

Octavian
· 1
Octavian
Replies (3)
helpful
0
not helpful

The EVERYONE and EVERYONE (Autheticated) groups are built in groups that should not be removed!

All users should belong to these 2 groups except of the anonymous user.

The difference between the 2 is that the first is for unauthenticated users (anon) and the 2nd is for all logged in users.

In version 3.1 you will be able to set the default for the visibility field.


Saar Cohen
· 5000
Saar Cohen
helpful
0
not helpful

OK, thanks for the info.

So to correct the problem what should we do now? Should we add back the "Everyone" with ID=1 to the "Global Groups" table?

When I've done that yesterday the "Issue Visibility" dropdown box listed items like:

Everyone

---Global Groups----

Everyone

Everyone (Authenticated)

etc.

so basically Everyone was listed twice. I don't remember has was after the migration though.

 

 

 


Octavian
· 1
Octavian
helpful
0
not helpful

Yes, this is fine.


Mark Wing
· 9108
Mark Wing