I don't like to mess IT operations with incidents. Under my point of view they're different worlds.
Anyway, if creating the 100 incidents just once, the easiest way is to use the data management tool and create the 100 incidents through this. It's easier that SOAP UI and it's the official way. Regards, Jose Manuel Huerta http://theremedyforit.com/ On Thu, Sep 13, 2012 at 10:19 PM, Sylvain YVON <[email protected]>wrote: > ** > > Kris, AFAIR you have a field in the interface form for the related CI. > Le 13 sept. 2012 22:02, "Wong, Kris" <[email protected]> a écrit : > > ** >> >> All,**** >> >> ** ** >> >> The incidents are to manually investigate and add information into the >> Asset CI’s. Basically I have a list of 100+ assets that are missing a few >> fields (Host name, serial number, etc.) that need to be added. I want to >> track progress on each asset to ensure that each is looked at.**** >> >> ** ** >> >> Maybe the suggestion to open 1 incident then associate 100 assets to it >> would work but the desire is to have 1 incident per asset.**** >> >> ** ** >> >> -Kris**** >> >> ** ** >> >> *Kristopher Wong* >> >> Business Analyst**** >> >> Information Technology Department**** >> >> General Dynamics Canada**** >> >> 613-596-7357 (Office)**** >> >> *[email protected]* >> >> ** ** >> >> *From:* Action Request System discussion list(ARSList) [mailto: >> [email protected]] *On Behalf Of *Jose Manuel Huerta Guillén >> *Sent:* September 13, 2012 11:10 AM >> *To:* [email protected] >> *Subject:* Re: [EXTERNAL] ITSM: Opening Multiple Incidents Easily**** >> >> ** ** >> >> ** Hi Kris,**** >> >> ** ** >> >> I think that if you give us more details about what you what to do, >> what's the objective, why do you want to do it, ... we would be able to >> provide you the best way to achieve it, and also advise you about the why >> you are solving your problem.**** >> >> ** ** >> >> For instance, If you want to create 100 tickets attached to the same CI >> because there is a list of operations to be done on the CI and each task >> must be assigned to a different support group, a Service request or a tree >> of taskes can be a better choice.**** >> >> ** ** >> >> Or if you want to create a 100 tickets of the same issue to multiple CI >> because it is a generalized incident, maybe one incident related to all >> CI's can be a better choice.**** >> >> ** ** >> >> Regards,**** >> >> ** ** >> >> Jose Manuel Huerta**** >> >> http://theremedyforit.com/ **** >> >> ** ** >> >> >> >> **** >> >> On Thu, Sep 13, 2012 at 5:03 PM, Stroud, Natalie K <[email protected]> >> wrote:**** >> >> ** **** >> >> Kristopher:**** >> >> **** >> >> Assuming you are talking about exactly the same CI for each ticket, >> templates can help streamline the entering of tickets, and I believe you >> can have them set a CI, though we have not used that aspect of the template >> functionality at our site. You do still, however, have to create each >> incident individually. I am not aware of a cloning feature in ITSM 7.6.04 >> that creates a new ticket based on the current ticket, which is a function >> we also had in our previous Remedy ticketing system.**** >> >> **** >> >> There may also be tricks that developers can do behind the scenes to >> create a bunch of tickets that I am not aware of, but I’ll let the >> developers here on the list speak to that point.**** >> >> **** >> >> Good luck!**** >> >> **** >> >> *Natalie Stroud***** >> >> SAIC @ Sandia National Laboratories**** >> >> ARS-ITSM Tester**** >> >> Albuquerque, NM USA**** >> >> [email protected]**** >> >> ITSM 7.6.04 SP2 – Windows 2008 – SQL Server 2008**** >> >> **** >> >> **** >> >> *From:* Action Request System discussion list(ARSList) [mailto: >> [email protected]] *On Behalf Of *Wong, Kris >> *Sent:* Thursday, September 13, 2012 7:41 AM >> *To:* [email protected] >> *Subject:* [EXTERNAL] ITSM: Opening Multiple Incidents Easily**** >> >> **** >> >> ** **** >> >> All,**** >> >> **** >> >> This is my first post although I’ve been reading for a while.**** >> >> **** >> >> I need to open 100+ incidents that are all essentially the same but need >> each individual one to have a relationship to a pre-populated CI. Is there >> an easy way to do this?**** >> >> **** >> >> I am on a new 7.6.04 instance and am sure at my previous company we had >> this functionality. Let me know if I am missing something as I’ve new to >> 7.6.04. Thanks**** >> >> **** >> >> -Kris**** >> >> **** >> >> *Kristopher Wong***** >> >> Business Analyst**** >> >> Information Technology Department**** >> >> General Dynamics Canada**** >> >> 613-596-7357 (Office)**** >> >> *[email protected]***** >> >> **** >> >> *The information contained in this e-mail message is PRIVATE. It may >> contain confidential information and may be legally privileged. It is >> intended for the exclusive use of the addressee(s). If you are not the >> intended recipient, you are hereby notified that any dissemination, >> distribution or reproduction of this communication is strictly prohibited. >> If the intended recipient(s) cannot be reached or if a transmission problem >> has occurred, please notify the sender immediately by return e-mail and >> destroy all copies of this message. >> Thank you.** ***** >> >> _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_**** >> >> _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ **** >> >> ** ** >> >> _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ **** >> >> The information contained in this e-mail message is PRIVATE. It may >> contain confidential information and may be legally privileged. It is >> intended for the exclusive use of the addressee(s). If you are not the >> intended recipient, you are hereby notified that any dissemination, >> distribution or reproduction of this communication is strictly prohibited. >> If the intended recipient(s) cannot be reached or if a transmission problem >> has occurred, please notify the sender immediately by return e-mail and >> destroy all copies of this message. >> Thank you. >> <#139c149a161bf0e3_139c13a116dadee2_> >> _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ > > _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
