Hi Afi,

Is this a new Bugzilla 4.x installation or you upgraded Bugzilla from older
version? If you upgraded from earlier release - there are migration steps
for the workflow & state names - that's described in Bugzilla's
instructions.
(You can see & edit your Bugzilla workflow from your Bugzilla administration
web interface).

Regards,
Yavor

On Fri, Jul 1, 2011 at 11:29, Amouzou, Afi <[email protected]>wrote:

>
> Hello,
>
> I am using Bugzilla 4.0.1 with the default Bug Workflow. And I applied the
> patch scmbug_bugzilla_custom_status_workflow.patch from *
> http://www.mail-archive.com/[email protected]/msg02681.html*<http://www.mail-archive.com/[email protected]/msg02681.html>.
> I also add the bug_status-map configuration to the daemon.conf. The Bug
> Workflow in my Bugzilla is the same as the one in the bug_status-map
> configuration. I didn´t change anything in the resolution template part. But
> if I tried to commit with status 9: resolved fixed I get the error message:
> * Scmbug* error 7: Resolving bug '9' from state 'IN_PROGRESS' to state
> 'resolved'
> would violate the workflow of the bug-tracker. Instead, the resolution
> could be changed to the . I have tried all possible bug status in my
> workflow it is not working. Is there something else to change before I can
> use the Bugzilla 4 Workflow?
>
>
>  Best Regards,
>
> *Afi Ahoefa Amouzou
> *FTS TSP DCS R&D QA1
>
> *FUJITSU*
> Fujitsu Technology Solutions GmbH
> Bürgermeister Ulrich Straße 100
> 86199 Augsburg Deutschland
> Tel: +49 821 804-1402
> Email: *[email protected]* <[email protected]>
> Web: *ts.fujitsu.com* <http://ts.fujitsu.com>
> Company Info: 
> *de.ts.fujitsu.com/imprint*<http://de.ts.fujitsu.com/imprint.html>
>
>
>
>
> _______________________________________________
> scmbug-users mailing list
> [email protected]
> http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
>
>
_______________________________________________
scmbug-users mailing list
[email protected]
http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users

Reply via email to