It's all about the answers!

Ask a question

Changed the process attached to our project by mistake


Adil Chahid (45524118) | asked Mar 26 '09, 6:11 p.m.
Hi all,
we have this old RTC project that was defined with the Eclipse Way Process.
We did customize in house the SCRUM process and started using it in most of our RTC projects.
We did by mistake paste the process configuration (XML) of the customized SCRUM process to the Eclipse way and saved the project configuration.

This did remove some WI fields mappings:
for instance, the users were not assigned anymore to any process role since the process roles are different.
The priority list did also change, the state of the ticket also changed even if some states were labeled the same.

So one of our resources started mapping the users with the new roles and started creating new WI.
We did finally realized the problem so we decided to roll back to the old process.

Unfortunalty some fields in the newly created Work Items were in a weird state, because of the fact that their calues were not defined anymore in the Eclipse way process.
For instance,

The State of the WI was set to uninitialized.
The Severity field of the WI was set to Literal.Severity.4
The Priority field of the WI was set to Literal.Priority.2
and so on...

So here's what we did found to fix those.
We switched all the erogenous WI to another type of WI: from Task to Planned WI for instance.
And we then switched them back to Task.
This reconciled the filelds with the right values.
I hope that this information is gonna help so folks out there.

Take care all,

2 answers



permanent link
Jared Burns (4.5k29) | answered Mar 27 '09, 4:27 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
On Thu, 26 Mar 2009 22:19:53 +0000, Thunder wrote:

Hi all,
we have this old RTC project that was defined with the Eclipse Way
Process.
We did customize in house the SCRUM process and started using it in most
of our RTC projects.
We did by mistake paste the process configuration (XML) of the
customized SCRUM process to the Eclipse way and saved the project
configuration.

This did remove some WI fields mappings: for instance, the users were
not assigned anymore to any process role since the process roles are
different. The priority list did also change, the state of the ticket
also changed even if some states were labeled the same.

So one of our resources started mapping the users with the new roles and
started creating new WI.
We did finally realized the problem so we decided to roll back to the
old process.

Unfortunalty some fields in the newly created Work Items were in a weird
state, because of the fact that their calues were not defined anymore in
the Eclipse way process.
For instance,

The State of the WI was set to
uninitialized. The
Severity field of the WI was set to
Literal.Severity.4 The
Priority field of the WI was set to
Literal.Priority.2 and so on...

So here's what we did found to fix those. We switched all the erogenous
WI to another type of WI: from Task to Planned WI for instance.
And we then switched them back to Task. This reconciled the filelds with
the right values. I hope that this information is gonna help so folks
out there.

Take care all,


Using the I provided in your question about browsing the history, you'll
be able to view the previous state of your process XML to restore it.


--
Jared Burns
Jazz Process Team

permanent link
Adil Chahid (45524118) | answered Mar 30 '09, 3:21 p.m.
On Thu, 26 Mar 2009 22:19:53 +0000, Thunder wrote:

Hi all,
we have this old RTC project that was defined with the Eclipse Way
Process.
We did customize in house the SCRUM process and started using it in most
of our RTC projects.
We did by mistake paste the process configuration (XML) of the
customized SCRUM process to the Eclipse way and saved the project
configuration.

This did remove some WI fields mappings: for instance, the users were
not assigned anymore to any process role since the process roles are
different. The priority list did also change, the state of the ticket
also changed even if some states were labeled the same.

So one of our resources started mapping the users with the new roles and
started creating new WI.
We did finally realized the problem so we decided to roll back to the
old process.

Unfortunalty some fields in the newly created Work Items were in a weird
state, because of the fact that their calues were not defined anymore in
the Eclipse way process.
For instance,

The State of the WI was set to
uninitialized. The
Severity field of the WI was set to
Literal.Severity.4 The
Priority field of the WI was set to
Literal.Priority.2 and so on...

So here's what we did found to fix those. We switched all the erogenous
WI to another type of WI: from Task to Planned WI for instance.
And we then switched them back to Task. This reconciled the filelds with
the right values. I hope that this information is gonna help so folks
out there.

Take care all,


Using the I provided in your question about browsing the history, you'll
be able to view the previous state of your process XML to restore it.


--
Jared Burns
Jazz Process Team

Hi, yes you're right!
the point is to not change the state of the Work Items once there was a mistake with the process.
I'd even suggest to remove the rights to the users during the process rollback operation.

Take care all,

Your answer


Register or 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.