
Dear Amedee,
These are the virtues of Open Source. There is no way you are entitled
to support or that anyone should fix any issues that you discover with
OTRS. Let me quote the GNU license under which OTRS is distributed:
NO WARRANTY
11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
REPAIR OR CORRECTION.
So this means - in the case of OTRS - that of course you can enter a
bug in Bugzilla and that someone MIGHT work on the bug but it might
also be open in there for a couple of months or years before it is
fixed. If you would browse Bugzilla you will see that there are
several bugs open for quite some time. That's because no one
apparently cares enough for them to fix it... or has enough time to
fix all bugs.. or..
If you would want to have commercial support for OTRS you have several
options, you can refer to this URL: http://otrs.org/support/
And if you want this very bug resolved and no one seems to work on
your bugzilla issue, you can fix the issue yourself or hire a
programmer to fix it and attach it to the bug. In that case, it might
(or might not) be included in the next release of OTRS.
And of course there might be the discussion for what is 'work as
intended'... but that's a different one.
Regards,
--
Michiel Beijen
Software Consultant
+31 6 - 457 42 418
Bee Free IT + http://beefreeit.nl
On Tue, Dec 16, 2008 at 19:06, Amedee Van Gasse
On Thu, November 27, 2008 10:57, Amedee Van Gasse wrote:
On Mon, November 3, 2008 16:53, Ugo Bellavance wrote:
Amedee Van Gasse a écrit :
On Mon, November 3, 2008 15:20, Ugo Bellavance wrote:
Amedee Van Gasse a écrit :
Hello,
When I merge one ticket into the other, the old ticket is changed to: (for example)
Merged Ticket 2008102110000024 to 2008102110000015.
OTRS version is 2.3.2.
Is this normal behavior? I have used OTRS in the past, and then it didn't leave any trace of the old ticket after a merge. (except of course in the new ticket)
If this can be turned off, how does that work? I agree... I think that once it is merged, the contents of the source ticket should be copied in the destination ticket and the source ticket should not be displayed anymore.
Ugo
Thank you Ugo. So now my question is: how can I make OTRS work that way?
I guess the best way would be to create a bug in the bugzilla...
Hello,
I reported a bug in the bugzilla on 7/11, what should I do next?
http://bugs.otrs.org/show_bug.cgi?id=3437
_______________________________________________ OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs