Customizing help desk ticket

builders

We are wanting to customize our help desk form entries. Our marketing department would like collect information regarding signs they are wanting to print.

something like what is listed below:

----------

What is the sku number?

What type of sign? 8 1/2 x 11, water proof, etc

what content is on the sign, what does it say specifically?

person of contact for the sign

---------

We are wanting to us OS ticket to do this, but are unsure of the best way to approach this.

We currently have OS ticket for our IT help desk tickets, but wasn't sure if we altered the ticket submission screen to add more fields, if these fields would change the "ticket submission" screen for not only the Marketing department portion of OS Ticket, but also the IT and HR department areas. This, we do not want to happen. We want these extra fields to be only within the Marketing area.

Is this possible with this system, if so, what would be the best way to approach this. Any thoughts/ideas are greatly appreciated.

Thank you for your time,

Nathan

ntozier

I have a IT ticketing system in place here where I work. It's heavily modified from the stock version. its support.domain.ext. I also have my test bed which is devel-support.domain.ext. Both share the same database. I do my development on dev-support. And once I'm content that it works the way I want it to, I move the source over. I've done things like add fields. You could replicate this type of setup if you WANT to have the same data in each instance. If you do not need to though, you could simply setup another database and point the new Sales version to the different database.

I hope this helps answer your question(s). :)

ntech

I have a IT ticketing system in place here where I work. It's heavily modified from the stock version. its support.domain.ext. I also have my test bed which is devel-support.domain.ext. Both share the same database. I do my development on dev-support. And once I'm content that it works the way I want it to, I move the source over. I've done things like add fields. You could replicate this type of setup if you WANT to have the same data in each instance. If you do not need to though, you could simply setup another database and point the new Sales version to the different database.
I hope this helps answer your question(s). :)

Could I see how you have your ticket system setup for ideas? I would really like to get a computer check in system going for my retail shop.