It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,837

question asked: Dec 14 '10, 4:26 a.m.
question was seen: 3,974 times
last updated: Dec 14 '10, 4:26 a.m.

Related questions

Why are changes to components not handled as other changes

0
Hampus Wingren (31●10●8) | asked Dec 14 '10, 4:26 a.m.
Hi,

I find this to be really strange. Weve set a precondition that you cannot deliver any change without a WI, however, adding, renaming or removing a component does not adhere to these rules. A component can potentially contain a lot of files and should IMHO be treated as any other change.

Am I missing some crucial concept definition of components?

Regards,
Hampus

One answer

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Nick Edgar (6.5k●7●11) | answered Dec 14 '10, 10:56 a.m.
JAZZ DEVELOPER
No, you're not missing any concept. This is a gap in the SCM preconditions support.
For more details see 110283: all delivery preconditions should offer to apply onto to a set of components.

The only workaround I'm aware of is to reduce the permissions on the component operations to restrict them to people who can be trusted to ensure all changes meet the preconditions. For a component addition, one could add the initial baseline, then deliver the changes separately.

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.