Bugzilla – Full Text Bug Listing
| Summary: | Submitting a bug to a Bugzilla 4.0 repository fails | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Alfonso Muñoz-Pomer <alfonso.munozpomer> |
| Component: | Mylyn | Assignee: | Frank Becker <eclipse> |
| Status: | RESOLVED WORKSFORME | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | eclipse |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
Alfonso Muñoz-Pomer
For the record, adding the value 'START' in the Bugzilla fields doesn't solve the issue, as Mylyn says that you can't file a new bug with 'START' as status. I tried because I saw that the issue with 'NONE' in version 3.6 was solved adding it to Bugzilla (I read about it after I upgrade to 3.7, so maybe I'll downgrade to 3.6 for the time being). After downgrading to 3.6 the error persists. Additionally 'NONE' can't be added to Bugzilla 4, as it's an internal field. Can you provide more information about your Bugzilla instance? Is it publicly accessible to help us reproduce the problem? Our Bugzilla installation is at https://bitoechvana.uv.es/bugzilla It's a private repository, but I could create a testing account if that can help you locate the bug. Also, if you could give me brief directions as how to extract more informative messages, that's fine with me, too. Sorry, the URL is https://biotechvana.uv.es/bugzilla It seems that when Mylyn submits a task to Bugzilla, the status NONE is not recognised and it should be NEW. Same thing if you mark the bug with as “Accept“, it says “There is no status named ‘ACCEPT’”, and I guess that instead of ACCEPT the status should be “ASSIGNED” (as it says besides the checkbox). If you’d like an account in our Bugzilla repository to test the issue I can create one for you. Let me know and I’ll email the details to you. (In reply to comment #7) > If you’d like an account in our Bugzilla repository to test the issue I can > create one for you. Let me know and I’ll email the details to you. Please create a account for me and tell me in what Product / Component i can create some test bugs. (In reply to comment #4) > Our Bugzilla installation is at https://bitoechvana.uv.es/bugzilla > > It's a private repository, but I could create a testing account if that can > help you locate the bug. > > Also, if you could give me brief directions as how to extract more informative > messages, that's fine with me, too. Can you please tell my how your workflow is defined. (maybe you create a picture for the administration page of the workflow) I nee th know the ststus values and the posible trasitions. Hi, I’m really, really sorry for not replying. Somehow I missed the email notifications for your last two comments (I think I got them mixed with the autowhine mails generated by our Bugzilla installation and marked them all as read). In any case I think the error was caused by a buggy Bugzilla installation (more specifically something to do with the Perl modules needed by Bugzilla). I located some inconsistencies which, by the way, I managed to solve only by upgrading to Bugzilla 4.2rc1, and now Mylyn works perfectly. Sorry for the delay and thanks for such an amazing plug-in. see comment#10 |