Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

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

1. Rename INVALID state to OLD INVALID.
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

0 votes



3 answers

Permanent link
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

1. Rename INVALID state to OLD INVALID.
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

0 votes


Permanent link
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 Final

Must be something else. Any other Idea
Thanks
erwin

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

1. Rename INVALID state to OLD INVALID.
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

0 votes


Permanent link


It seems to be known as bug :-)

 

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 :-(

0 votes

Your answer

Register or log in to post 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.

Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details

Question asked: Apr 17 '12, 3:50 a.m.

Question was seen: 3,620 times

Last updated: Jul 04 '12, 4:23 a.m.

Confirmation Cancel Confirm