Add multiple CI's to a Change Ticket

[nortonxnorris]

We have regular patching which involve around 100 CI's. What is the best way to add/associate the CI's to my change ticket?

[Michael Fry1]

For our regular patching we use Templates to create the Change and any Change tasks plus the CI's involved with that change. It's a little more administration on templates, but if they are setup with good naming convention, then it's not too bad. We use scheduled job to launch all the templates.

[kungfuu72]

I agree that a template would do good for this if you are tired of continually doing this every single time a patch goes out. Sure, creating the template will consume a bit of time the first time, but after that, its just one click. You can also update this template as needed.

[hima6]

If you are using Record Producer to create a Change Request use Slush Bucket(List Collector) to select multiple CI's.

Regards,

Hima Pallela.

[shill]

At my previous employer, we used a 'Copy Change' UI action so the admins could reuse the latest change. If they needed to add a CI or change something, they could then use the newer change request to copy the next one.

For those using a template, how do you populate the affected CI related list via the template?

Note that Geneva introduces a new 'Copy Change' UI action.

[Blaze2]

Create and save the Change

Scroll down to the Affected CI Related List

If you get too many options, you can always filter