CHARM - controlling task creation for CD in to be tested

[fuso_andrea]

Hi people,

I would like to share the following CHARM issue.

Developers involved in my project are a lot.

We use CDs (NC) for developing in an implementation project,

According to ChaRM standard, when develops end CDs are set by developers in "to be tested" status for testing porpouse in QUA (and TofC are imported in QUA).

Sometimes in the meantime it happens that an other developer logs in dirctly in DEV and open another task under the TRs that belong to the NC.

So my question is: is there a way to avoid developer modify the TR adding a new task ?

At list is there a best practice you can suggest to me?

Force developer to log in dirctly in SM is a affordable solution?

Thanks

Giovanni

[Former Member · Accepted solution]

Hi Giovanni,

have you considered to remove the authorization to create tasks for all developers in DEV?

Tasks created via SolMan use the authorization of the RFC-User of the TMW-RFC to create tasks, so you could still create tasks from SolMan but not in DEV directly.

Regards,

Christoph

[fuso_andrea · Accepted solution]

Interesting suggestion,

I can submit to the customer.

Of course SM availability becames very important.

Giovanni

[andreas_mann3]

or do you mixed sth up.

TofC are imported in QA and tested. But there's another error to correct.

So when I now change the corresp. program a new task is created automatically to the TR, althoug I've mo authorization to create a task!

grx

A.

[Former Member]

Hi Andreas,

can you give more details about your interesting suggestion?

Cheers,

Bob