Looking for a patch to 1.0.7


#1

Hi everyone,

I’m looking for some 1.0.7 patches to make my life easier…
I know this is very probably treated in RT2, but if RT2 was
production quality, it would be released, right :wink:

The major problem I have is to see that I only get one ticket
per contract/user/whatever. I’ll have a lot of tickets not
associated with a contract/user/whatever, but if one is, I want
only that one. So, essentially, to a free-form string, if
necessary just a number, I want to associate one and only one
ticket. Just as we have the box field in which we can enter a
ticket number and go to the corresponding ticket, so do I want
a box in which I can enter my free-form string and go to the
corresponding ticket. I don’t like the idea of using the ticket
subject, since that’s the mail subject, but I’m thinking of it.

That would be enough for my immediate needs; of course it would
be nicer if, for example, when there is no corresponding ticket,
one is created for the free-form string in question; if that is
the only way to create a liason between ticket and free-form
string that means that uniqueness is easily ensured, and that
operators will have a minimum of hoops to jump through.

Does anyone have such a patch somewhere? Any pointers,
something to get me started? No problem if some hacking at the
code is needed, I’d do the whole thing myself, it’s simply that
I haven’t yet dared to muck around too much in the code…


#2

This is probably more apropriate for rt-devel, but there is a
field in the each_req table called ‘alias’ that was intended for
just such a use. to make this actually, useful, you’d
want to add a check on the ticket loading routines to 'resolve’
the alias…and a web or cli frob to let you edit ‘alias’.

    jesseOn Tue, Mar 06, 2001 at 04:14:02PM +0100, Lorens Kockum wrote:

Hi everyone,

I’m looking for some 1.0.7 patches to make my life easier…
I know this is very probably treated in RT2, but if RT2 was
production quality, it would be released, right :wink:

The major problem I have is to see that I only get one ticket
per contract/user/whatever. I’ll have a lot of tickets not
associated with a contract/user/whatever, but if one is, I want
only that one. So, essentially, to a free-form string, if
necessary just a number, I want to associate one and only one
ticket. Just as we have the box field in which we can enter a
ticket number and go to the corresponding ticket, so do I want
a box in which I can enter my free-form string and go to the
corresponding ticket. I don’t like the idea of using the ticket
subject, since that’s the mail subject, but I’m thinking of it.

That would be enough for my immediate needs; of course it would
be nicer if, for example, when there is no corresponding ticket,
one is created for the free-form string in question; if that is
the only way to create a liason between ticket and free-form
string that means that uniqueness is easily ensured, and that
operators will have a minimum of hoops to jump through.

Does anyone have such a patch somewhere? Any pointers,
something to get me started? No problem if some hacking at the
code is needed, I’d do the whole thing myself, it’s simply that
I haven’t yet dared to muck around too much in the code…


rt-users mailing list
rt-users@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-users

jesse reed vincent – root@eruditorum.orgjesse@fsck.com
70EBAC90: 2A07 FC22 7DB4 42C1 9D71 0108 41A3 3FB3 70EB AC90

There are no supercomputer applications that are solvable that cannot be solved
in finite time using a fucking TRS-80 with approprite disk/tape drives. Zero.
-Tanj