#204 — hardcoded Itreation Workflow Name

by Stefan Eletzhofer — last modified Apr 28, 2010 08:38 PM

State	Resolved
Version:	2.0.2
Area	Process
Issue type	Bug
Severity	Medium
Submitted by	Stefan Eletzhofer
Submitted on	Feb 01, 2010
Responsible	—
Target release:	—

Return to tracker

The Products.eXtremeManagement.browser.management.py uses a hard-coded
name for the Iteration WF ID to get the iteration history. This
breaks, if iterations follow a custom workflow.

Steps to reproduce:: Copy the 'eXtreme_Iteration_Workflow' in the ZMI, assign the Iteration CT
to the copy, issue some Iteration WF action, go to the "planned iterations"
link.

Added by Stefan Eletzhofer on Feb 01, 2010 11:27 AM

should be fixed in r110068.

Added by Maurits van Rees on Apr 28, 2010 08:38 PM

Issue state: Unconfirmed → Resolved

Looks good, thanks.

No responses can be added.