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.




Edit Issue Bug and Request

visual-studio
add-ons

We are utilizing Gemini 3.5.3 and VS 2008 Plugin 1.5.4.

After an Issue is opened in Edit mode, modified, and a Save & Close executed, no changes appear to be committed back to the database.

The ability to add comments is unaffected.

Secondarily, is it possible to display more columns (specifically the assigned resources) within the plugin?

Thanks.

David Singleton
· 1
David Singleton
Replies (10)
helpful
0
not helpful

I would also like to see the "Fixed For Version" field.


David Singleton
· 1
David Singleton
helpful
0
not helpful

Ensure that PUT & DELETE verbs are added to the .ASHX extension within IIS for your Gemini web application. Please refer to section 9.5 of the Gemini Installation Guide.

As for your second question, this is not possible at the moment.



Bikram
· 1
Bikram
helpful
0
not helpful

Sorry for taking so long to reply.

The Gemini web application is properly configured (with ALL verbs added).

Adding comments works. Creating entirely new issues works. Editing and saving and issue appears to work, but does not.

Thank you for your efforts in resolving this issue.


David Singleton
· 1
David Singleton
helpful
0
not helpful

Can you please send the output from DebugView when doing the edit?

http://technet.microsoft.com/en-us/sysinternals/bb896647.aspx


Saar Cohen
· 5000
Saar Cohen
helpful
0
not helpful

No problem Saar. Here is the DebugView output. This was generated when I doubleclicked on an issue, clicked Edit, modified the Risk field, and then clicked Save & Close.

00000000 0.00000000 [340] CounterSoft Gemini: Start SetCurrentIssue 00000001 0.00024165 [340] CounterSoft Gemini: SetCurrentIssue: TOOLS-63 00000002 0.56521654 [340] CounterSoft Gemini: Start grdIssuesCellDoubleClick
00000003 0.56530315 [340] CounterSoft Gemini: Start SetCurrentIssue 00000004 0.56541348 [340] CounterSoft Gemini: SetCurrentIssue: TOOLS-63 00000005 0.58890337 [340] CounterSoft Gemini: Start OpenIssueDetailForm 00000006 91.36093140 [340] CounterSoft Gemini: Start SetCurrentIssue 00000007 91.36103058 [340] CounterSoft Gemini: SetCurrentIssue: TOOLS-63 00000008 91.36111450 [340] CounterSoft Gemini: Start LocalizeIssueGrid
00000009 91.36191559 [340] CounterSoft Gemini: End LocalizeIssueGrid 00000010 91.36199951 [340] CounterSoft Gemini: End OpenIssueDetailForm
00000011 91.36208344 [340] CounterSoft Gemini: End grdIssues
CellDoubleClick


David Singleton
· 1
David Singleton
helpful
0
not helpful

Hello David.

Are you able to modify the same issue from Gemini web app?

Please provide a screen shot of your All Verbs (.ASHX) configuration from IIS. Email to support at countersoft dot com.


Bikram
· 1
Bikram
helpful
0
not helpful

Yes, I can edit the issue via the web app.

I'll screen capture the those screens and send them on.

Thanks again.


David Singleton
· 1
David Singleton
helpful
0
not helpful

The screen caps have been sent.

Thanks.


David Singleton
· 1
David Singleton
helpful
0
not helpful

We have responded via email to your screen shots email.

Regards


Bikram
· 1
Bikram
helpful
0
not helpful

For the benefit of others that may read this thread...

Testing our VS plugin installation to your (Countersoft's) sandbox revealed no issues- everything worked appropriately.

Testing our VS plugin against our dev sandbox also revealed no issues.

Our production instance is different from both in that it authenticates via Windows authentication.

However, we do have a second production instance of Gemini that points to the same database backend using Forms authentication. It was established to get around Subversion integration/configuration issues.

When the VS plugin uses that instance, it works fine.

This appears to be either a Windows authentication issue or an issue due to the configuration differences of the two sites.

As a workaround, our developers will use the Forms authenticated production site.

Thanks.


David Singleton
· 1
David Singleton