Process change not fully propagated
We have about 10 Project using the same Process ( Use the process from another project area for this project area)
Due to a known error in the Taskboard handling (https://jazz.net/forums/viewtopic.php?p=61551) I planned to fix the issue doing following steps using eclipse client for the Task Workflow 2. Add a new state INVALID a 3. Add new action MOVE with Target INVALID 4. Delete Action INVALIDATE 5. Do a query for anything with a status of OLD INVALID and apply action MOVE 6. Delete the state of OLD INVALID. 7. Rename action MOVE to INVALIDATE Troubles started by action 5). For what ever reason the change was not propagated to all Projects. Some where fine, on some Project the MOVE did end in state NEW!! and other Projects had still the "old" workflow active. After some hours waiting, there where more Projects correctly propagated But after 20hours there are still a few with the "old" Workflow Thanks erwin Has somebody any Idea how this all works, how I can force the change to be propagated. If possible without stop/start. Thank you erwin |
3 answers
Hello Erwin,
It sounds like some of the project areas are overriding the shared process. This can happen if they were not created using Unconfigured Process template. Open a project area that has the old workflow active in the Eclipse project area editor. Click on the Process Configuration tab. Go to Work Items > Workflows. If the workflow shows in the editor, it means that the project area is overriding what has been defined in the provider. You will need to edit the XML source to remove the workflow. Martha Jazz Developer, Process Team We have about 10 Project using the same Process ( Use the process from another project area for this project area) Due to a known error in the Taskboard handling (https://jazz.net/forums/viewtopic.php?p=61551) I planned to fix the issue doing following steps using eclipse client for the Task Workflow 2. Add a new state INVALID a 3. Add new action MOVE with Target INVALID 4. Delete Action INVALIDATE 5. Do a query for anything with a status of OLD INVALID and apply action MOVE 6. Delete the state of OLD INVALID. 7. Rename action MOVE to INVALIDATE Troubles started by action 5). For what ever reason the change was not propagated to all Projects. Some where fine, on some Project the MOVE did end in state NEW!! and other Projects had still the "old" workflow active. After some hours waiting, there where more Projects correctly propagated But after 20hours there are still a few with the "old" Workflow Thanks erwin Has somebody any Idea how this all works, how I can force the change to be propagated. If possible without stop/start. Thank you erwin |
Hi Martha
"one never writes enough in a 'defect'description" All projects except one where created as unconfigured. The one based on scrum templates was edited in the xml sources by copy paste from an unconfigured one The Template process is set at least for the different parts of Work items as Must be something else. Any other Idea Thanks erwin Hello Erwin, We have about 10 Project using the same Process ( Use the process from another project area for this project area) Due to a known error in the Taskboard handling (https://jazz.net/forums/viewtopic.php?p=61551) I planned to fix the issue doing following steps using eclipse client for the Task Workflow 2. Add a new state INVALID a 3. Add new action MOVE with Target INVALID 4. Delete Action INVALIDATE 5. Do a query for anything with a status of OLD INVALID and apply action MOVE 6. Delete the state of OLD INVALID. 7. Rename action MOVE to INVALIDATE Troubles started by action 5). For what ever reason the change was not propagated to all Projects. Some where fine, on some Project the MOVE did end in state NEW!! and other Projects had still the "old" workflow active. After some hours waiting, there where more Projects correctly propagated But after 20hours there are still a few with the "old" Workflow Thanks erwin Has somebody any Idea how this all works, how I can force the change to be propagated. If possible without stop/start. Thank you erwin |
My solution, and it works fine, is to go to each project area, modify the description, save. Doing this enforce the process to be reloaded and re-cached.
Only problem ist when you start to have 40 Projects, like we have today :-( |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.