Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 315104 - Problem with custom initial state for Bugzilla
Summary: Problem with custom initial state for Bugzilla
Status: RESOLVED DUPLICATE of bug 259291
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Mylyn (show other bugs)
Version: 3.3   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Mylyn Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-31 11:46 EDT by Tobias F CLA
Modified: 2010-05-31 15:49 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Tobias F CLA 2010-05-31 11:46:54 EDT 
Build Identifier: 20100218-1602

Hello,
I'm using Bugzilla 3.6 with Mylyn 3.3.3.v20100330-0100.

The problem is that I can't create new bugs in Bugzilla because I get an "You are not allowed to file new bugs with the NEW status." error.

In the Bugzilla workflow I changed the initial state to allow only UNCONFIRMED. Because I wan't that every bug has to be confirmed from a programmer before it changes to NEW.
Now I can't create bugs with Mylyn because it looks like Mylyn uses allways NEW as initial state for my bug.

So far I couldn't find anny setting to change this in Mylyn or in Bugzilla.

Reproducible: Always

Steps to Reproduce:
1. Go to the 'Edit Workflow' Admin Page in Bugzilla
2. Change the '{Start}' line so that only UNCONFIRMED is checked.
3. Create new Bug using Mylyn
-> this results in the error.
Comment 1 Frank Becker CLA 2010-05-31 15:32:33 EDT 
I did not know if this is duplicate of bug# 311966 or bug# 259291.

But both are for target Mylyn 3.5
Comment 2 Steffen Pingel CLA 2010-05-31 15:49:22 EDT 
Yes, let's track that on bug 259291. Tobias, please feel free to add a comment about your specific case to that bug.

*** This bug has been marked as a duplicate of bug 259291 ***