Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 350059

Summary:

Mylyn Bugzilla connector is unable to submit changes to bug reports

Product:

z_Archived

Reporter:

Juan Camilo Prada <juankprada>

Component:

Mylyn

Assignee:

Mylyn Inbox <mylyn-inbox>

Status:

RESOLVED WORKSFORME

QA Contact:

Severity:

major

Priority:

CC:

eclipse, juankprada

Version:

unspecified

Target Milestone:

---

Hardware:

OS:

Linux

Whiteboard:

Attachments:

Description	Flags
output from config	none
bug Id output	none

Description Juan Camilo Prada

2011-06-22 10:17:12 EDT

Build Identifier: 20110615-0604

I have a bugzilla 3.1.4 installation which i tried to synchronize with mylyn. I can make queries and get all the bugss assigned to me and I can see the details of each bug.

The problem is when submiting a change to any bug. An example is that if i try to change the status to fixed i get an error that says:

"An unknown repository error has occurred: resolution not allowed" 

Clicking on that error opens a small window which tries to render a bugzilla page that displays in red:

"You cannot set a resolution for open bugs." which is something weird as I'm actually trying to change the status to RESOLVED.


If the bug is assigned and I'm the one who should accept the bug something different happens if I set it as  "Leave as New" or "Accept (Change status to ASSIGNED)". 

In this case when submitting i get the following error:

"An unknown repository error has occurred: internal error"

and again the small window appears with the following red message:

"A legal Resolution was not set."

which is again weird as I'm not setting any resolution to the bug as i havent changed its status to RESOLVED.

I can create new bugs and submit them though, so I'm not sure why I cant edit any other bug that is already in bugzilla.

Reproducible: Always

Steps to Reproduce:
1. Open the bug from Task List
2. Change the bug status or leave it as NEW
3. Submit the bug

Comment 1 Frank Becker

2011-06-22 12:50:18 EDT

Is your bugzilla 3.1.4 installation accessible from the public?

Comment 2 Juan Camilo Prada

2011-06-22 13:41:04 EDT

Hi

No it is only accessible from the intranet. Should I look for something in particular?

thanks

Comment 3 Frank Becker

2011-06-22 13:49:55 EDT

(In reply to comment #2)
> Hi
> 
> No it is only accessible from the intranet. Should I look for something in
> particular?
> 
> thanks

Yes, can you please tell me if you use some custom values in your installation.

If possible you can send me the
1)  ../config.cgi?ctype=rdf result (xml as an textfile)
2) ../show_bug.cgi?id=<your bug ID>&ctype=xml result  (xml as an textfile)

Comment 4 Juan Camilo Prada

2011-06-22 13:55:56 EDT

Created attachment 198423 [details]
output from config

Comment 5 Juan Camilo Prada

2011-06-22 13:56:25 EDT

Created attachment 198424 [details]
bug Id output

Comment 6 Juan Camilo Prada

2011-06-22 13:57:25 EDT

attached the output of both commands.

I don't really know if there are custom values on the config, i'm not really familiar with bugzilla configuration.

Comment 7 Frank Becker

2011-06-23 05:43:00 EDT

Bugzilla 3.1.4 is an development release (see http://www.bugzilla.org/news/#release304) released 2008 May 4.

Can you update your installation to an supported version ( 4.0.1, 3.6.5, and 3.4.11)?

Please do not use Development versions for production! (see http://www.bugzilla.org/download/#numbering) 

We have ca. 30 points in ouwer sources where we do special thinks for an specific bugzilla version and I think we should nor track down the source of this problem for version thar has reach end of live.

Comment 8 Juan Camilo Prada

2011-06-23 07:44:48 EDT

Got it, gonna try to make the upgrade. As I said, I was not the one who configured this bugzilla installation so I don't know the reasons behind chosing a development release.

Anyway, thanks for your help

Comment 9 Steffen Pingel

2011-08-11 07:41:04 EDT

I'll mark this as resolved for now. Juan, please feel free to reopen if the problem persists after updating the Bugzilla instance.