359300 – submitting new bugs to Bugzilla 4.0 results in error: Submit failed: invalid status: There is no status named 'NONE'

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

Bug 359300 - submitting new bugs to Bugzilla 4.0 results in error: Submit failed: invalid status: There is no status named 'NONE'

Summary: submitting new bugs to Bugzilla 4.0 results in error: Submit failed: invalid...

Status:	RESOLVED FIXED

Alias:	None

Product:	z_Archived
Classification:	Eclipse Foundation
Component:	Mylyn (show other bugs)
Version:	unspecified
Hardware:	All Linux

Importance:	P1 critical (vote)
Target Milestone:	3.6.3
Assignee:	Frank Becker
QA Contact:

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:	337245 358906 359299
	Show dependency tree

Reported:	2011-09-28 16:05 EDT by Steffen Pingel
Modified:	2011-10-13 14:25 EDT (History)
CC List:	1 user (show)

See Also:

Attachments
error in task editor (22.11 KB, image/png) 2011-09-28 16:07 EDT, Steffen Pingel	no flags	Details
mylyn/context/zip (35.40 KB, application/octet-stream) 2011-09-29 15:48 EDT, Frank Becker	no flags	Details
View All 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 Steffen Pingel

2011-09-28 16:05:59 EDT

Steps:
1. Add https://bugs.eclipse.org/bugstest as a repository
2. Submit bug

The submission fails and an error is displayed in the task editor: Submit failed: invalid status: There is no status named 'NONE'.

Comment 1 Steffen Pingel

2011-09-28 16:07:50 EDT

Created attachment 204221 [details]
error in task editor

Comment 2 Steffen Pingel

2011-09-28 16:11:00 EDT

Frank, can you check why these actions are shown when creating new tasks? This is related to bug 358906 and bug 359299.

Comment 3 Frank Becker

2011-09-29 15:48:12 EDT

Steffen,

I have create an review http://review.mylyn.org/#change,67

Comment 4 Frank Becker

2011-09-29 15:48:15 EDT

Created attachment 204325 [details]
mylyn/context/zip

Comment 5 Steffen Pingel

2011-10-05 15:41:25 EDT

Frank, can you provide some more information how the proposed change fixes the problem? It's not quite obvious to me from the code review how that works.

Comment 6 Frank Becker

2011-10-06 04:30:31 EDT

We had some places where we assume that when we are running Bugzilla >= 4.0 we also have the new workflow.

1) BugzillaClient.getPairsForNew
    we add the Operation if it is not new_default. For the old workflow we here had NONE.
2) BugzillaTaskDataHandler.initializeNewTaskDataAttributes
    here we use the Bugzilla4.0 Start Status even if we had the old workflow. For the old workflow we need the start status from the repository configuration.
3) RepositoryConfiguration.getStartStatus
    should return status new for bugzilla >=4.0 and old workflow.

Hope this helps!

Comment 7 Steffen Pingel

2011-10-13 14:25:23 EDT

Thanks. I have committed the change to e_3_7_m_3_6_x and master.