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.




Scheduler Mailbox Processor Settings

emails

Hello again,

I am having issues with the configuration of the mailbox processors in the scheduler configuration file. Mainly to do with the Visibility of the issues that are created. The scheduler works fine but it seems that I'll send it an email, it creates an issue and sends me a notification that the issue has been created. Then I go into Gemini (not using the link in the email) and I can't see the issue anywhere. No other user on the system can either. I've set the VisibilityMemberType to 2 and Visibility to 3 or 1 (which from what I understand is Everyone(authenticated) and Everyone respectively). My understanding of those visibilities is that anyone can see them if they have those permissions which everyone on my system does. I'm finding that only the userid that is set can view them. That doesn't seem to make any sense. Is this the way it was designed or am I doing something wrong? I'm trying to create the issues to a general project using the anonymous user so that once it's created we can then move the issue to the proper project. But no one can see the created issues.

Here is the settings section of the mailbox processor portion of the config.

            ProjectID="2"
            UserID="-1"
            ComponentID="5"
            IssueType="4"
            IssuePriority="1"
            IssueSeverity="1"
            Visiblity="3"
            VisiblityMemberType="2"
            RiskLevel="1"
            DebugFile = "c:\GeminiPOP3log.txt"
            DebugMode = "False"

When I look at the issue using the link in the notification email the component id and all other settings are set properly, even the visibility, but it still can't be seen by everyone, authenticated or not.

KPaxton1182
· 1
KPaxton1182
Replies (2)
helpful
0
not helpful

Please make sure that you do not have the "view own issues" permission in the security scheme for that project.


Saar Cohen
· 5000
Saar Cohen
helpful
0
not helpful

yup that did it. Thanks!


KPaxton1182
· 1
KPaxton1182