release calss

[Former Member]

Hi ,

I have one issue , if we add a new chateristic to the class which in the existing release strategy, whether the release strategy picks the new characteristic values also or not?

As my understanding if we add new characteristic to the class in the exiting release strategy , the old strategy will not work.

one more question can we maintain two classes to one release strategy!!

Kindly repond immediately.

regards,

sudhakar

[Former Member]

Hi,

After you are adding the new charachteristics in a class,you have to add the values for the perticulat charecteristics in the release strategy so that while making PR / PO the system will consider these values(including the new value you entered) for picking up the strategy.

if you don't enter the values for the new charecteristics in the release strategy it will remain the old strategy so the system will pick the same.only after adding the vlues(by this you will be activating the charecteristics)it becomes the new strategy with the same strategy number.

It is not possible to have two strategies with same release group and same class.

if you are looking for two strategies with same class then you have to go for different release groups.

Still you have any doubts please let me know.

Reward If usefull.

Thanks and regards,

Batchu.

[Former Member]

Hi ,

Thanks for immediate response.

i will be maintaining the values for new characterisitic , but if you transport this new release strategy to the other client, whether it will have any impact on existing release strategy in that client.

[Former Member]

Hi

First of all u can not trasport release strategy from client to client There u need to add created charactaristic in available release strategy

Once it is added new PO will be triggered with new release strategy.For old PO old release strategy will be there.

If u r amending PO then based on criteria new release strategy will be picked for amended old PO

Vishal...

[Former Member]

Hi,

No problem u can transport to other client also,but u have to maitain all the values in the strategy seperately.

those values in the characteristics will not be transported.

Regards,

Batchu

[Former Member]

Hi ,

I have created the new characteristic and added to the class . then i created a release strategy . Then this strategy copied from config client to Dev client. After its moving its giving the error msg"error in classification for the relese strategy PRN1 of class type 032".

i checked this strategy is not appearing in in CL24N

After adding the release strategy values in the classfication throgh SPRO , then the strategy is appearing in CL24N.

Concern is whether this approch is correct or not ?

If this is ok , can i do the same thing in Production also.

please let me know , so that i can proceed for further release strategies.

please respond immediately.

regards,

sudhakar

[Former Member]

HI,

Your aproach is correct,YOu can o ahead for further transports.

all the best

regards,

Batchu

[ericsj]

I fthe class remain the same and only you add a new release strategy,once you enter the value to the release strategy classification, the values should be picks up. If you change the characteristic but you did not edit the release strategy classification characteric config than the new characteristic will not pickup.

You can only has different class for individual or Overall release (1 class for Release group of individual item release strategy and different class for Overall (Header) release strategy. You cannot have 2 class for a same release strategy.