Hi All,
I am just curious as to whether;
a) Anyone is using OTRS in conjunction with TFS/Visual Studio Online
b) Anyone had tried integrating the two
Basically we use OTRS to catch all client requests/bugs/issues etc and then create corresponding tasks/bugs etc in VSO to match these.
The problem I have with this is that it is asynchronous and disjointed. Completing the task in VSO obviously does not affect the ticket in OTRS etc.
I see no that VSO offers the use of REST to perform certain tasks and OTRS uses SOAP which is fairly similar if not heavier. Can these two sepak to each other? Would it be possible to build a web service on either end that would pas information back and forth?
Namely to create a task/bug in VSO if the ticket state of OTRS is changed to, say, 'VSO Task' or 'VSO Bug', passing the subject as the task title and the body as the body, the owner as the user and the customerid as the project name (these are matched already). Furthermore if the task/bug is then updated, I would like an article to be added to the ticket in OTRS detailing any changes.
OTRS VSO Integration
-
- Znuny newbie
- Posts: 23
- Joined: 26 Nov 2013, 10:50
- Znuny Version: 3.3.1
- Real Name: Tarn
- Company: Guccio Computer Consulting
-
- Moderator
- Posts: 10170
- Joined: 04 May 2010, 18:38
- Znuny Version: 5.0.x
- Location: SouthWest Florida, USA
- Contact:
Re: OTRS VSO Integration
If VSO sent an email to OTRS on complete, you could check this... With External Ticket Recognition or System Management you could arrange followup/close.tarnalcock wrote: Completing the task in VSO obviously does not affect the ticket in OTRS etc.
OTRS 6.0.x (private/testing/public) on Linux with MySQL database.
Please edit your signature to include your OTRS version, Operating System, and database type.
Click Subscribe Topic below to get notifications. Consider amending your topic title to include [SOLVED] if it is so.
Need help? Before you ask
Please edit your signature to include your OTRS version, Operating System, and database type.
Click Subscribe Topic below to get notifications. Consider amending your topic title to include [SOLVED] if it is so.
Need help? Before you ask
Re: OTRS VSO Integration
OTRS 3.4. will have a REST interface included
"Production": OTRS™ 8, OTRS™ 7, STORM powered by OTRS
"Testing": ((OTRS Community Edition)) and git Master
Never change Defaults.pm! :: Blog
Professional Services:: http://www.otrs.com :: enjoy@otrs.com
"Testing": ((OTRS Community Edition)) and git Master
Never change Defaults.pm! :: Blog
Professional Services:: http://www.otrs.com :: enjoy@otrs.com
-
- Znuny newbie
- Posts: 23
- Joined: 26 Nov 2013, 10:50
- Znuny Version: 3.3.1
- Real Name: Tarn
- Company: Guccio Computer Consulting
Re: OTRS VSO Integration
Thanks for the info jojo!jojo wrote:OTRS 3.4. will have a REST interface included
As far as I can see the versioning stopped at 3.3.9 and jumped to 4.1 beta. Is this correct, or am I being blind?
This is honestly the biggest breakdown in our systems at the moment. I would really find the REST interface to be very advantageous. Should I try 4.1, considering that this is a live ticketing system?
Re: OTRS VSO Integration
3.4 was renamed to OTRS4
currently it is in beta and should not be used for production
currently it is in beta and should not be used for production
"Production": OTRS™ 8, OTRS™ 7, STORM powered by OTRS
"Testing": ((OTRS Community Edition)) and git Master
Never change Defaults.pm! :: Blog
Professional Services:: http://www.otrs.com :: enjoy@otrs.com
"Testing": ((OTRS Community Edition)) and git Master
Never change Defaults.pm! :: Blog
Professional Services:: http://www.otrs.com :: enjoy@otrs.com
-
- Znuny newbie
- Posts: 23
- Joined: 26 Nov 2013, 10:50
- Znuny Version: 3.3.1
- Real Name: Tarn
- Company: Guccio Computer Consulting
Re: OTRS VSO Integration
Hi Guys,
I see that OTRS 4 is now listed as stable. I would like to try it out, first on a test server and then moved to production.
My ideas are the following though.
I could either;
A) Test OTRS and then roll it out on my current production server or;
B) Install OTRS on a test server, bring my data a across and make this my new production server if all works correctly.
Which course of action would you recommend?
Many Thanks
I see that OTRS 4 is now listed as stable. I would like to try it out, first on a test server and then moved to production.
My ideas are the following though.
I could either;
A) Test OTRS and then roll it out on my current production server or;
B) Install OTRS on a test server, bring my data a across and make this my new production server if all works correctly.
Which course of action would you recommend?
Many Thanks