Where to report bugs?

RT Users
1

Hello all,

I reported some bugs to rt-bugs@fsck.com but only received the automatic
reply. No other feedback since 6 weeks.

So I wonder whether the above is the correct address? Or where to report bugs?
Maybe rt-users, so that the issues can be discussed?

These are the issues I reported, maybe they are of interest to somebody, too.

  • special characters in queue names
  • Unknown field: Requestor.EmailAddress
  • Relogin necessary to see queue changes
  • ticket search reveals higher total number of found tickets than allowed to
    see

Also I have the problem (I unfortunately don’t remember whether it was
introduced between my switch from 3.4.4 to 3.6.0 or from 3.6.0 to 3.6.1) that
the links I added in local/html/Callbacks/MyCallbacks/Elements/Tabs/Default
like this:

$toptabs->{‘ZA’} = { title => “Help”,
path => “http://intranet-wiki/RT-Help” };

now will point to http://rt-web/http://intranet-wiki/RT-Help thus prepending
the RT URL and not using the URL directly (this worked before).

I put an HTML file into the local RT NoAuth space, which does a redirect to
the external URL, but I liked it better how it was before.

Cheers,
Stephan

inubit AG
integrating your business and IT
Tel +49.30.726112-300, Fax -100
http://www.inubit.com/su/public_key

2

Hello all,

I reported some bugs to rt-bugs@fsck.com but only received the automatic
reply. No other feedback since 6 weeks.

Oftentimes, this is because issues have already been discussed and/or
resolved on rt-users, sometimes, it’s just because we’re overworked. (If
you need commercial help and guaranteed response, that’s very doable,
but not what rt-users is about :wink:

So I wonder whether the above is the correct address? Or where to report bugs?
Maybe rt-users, so that the issues can be discussed?

Uusally discussing issues on rt-users first is the right thing.

These are the issues I reported, maybe they are of interest to somebody, too.

  • special characters in queue names

Ticket #?

  • Unknown field: Requestor.EmailAddress
  • Relogin necessary to see queue changes
  • ticket search reveals higher total number of found tickets than allowed to
    see

These three have already been discussed in depth on rt-users or
rt-devel. There’s a patch for the first. The second two are design
artifacts. The third one, I know I’ve responded in depth to several
tickets about why a good solution is hard and expensive
(computationally).

Jesse

3

Thanks for your comments, Jesse!

Hello all,

I reported some bugs to rt-bugs@fsck.com but only received the automatic
reply. No other feedback since 6 weeks.

Oftentimes, this is because issues have already been discussed and/or
resolved on rt-users, sometimes, it’s just because we’re overworked. (If
you need commercial help and guaranteed response, that’s very doable,
but not what rt-users is about :wink:

I see. Primarily I wanted to make sure that my feedback went to the right
place, so that developers at least know about the problems.

So I wonder whether the above is the correct address? Or where to report
bugs? Maybe rt-users, so that the issues can be discussed?

Uusally discussing issues on rt-users first is the right thing.

Ok.

These are the issues I reported, maybe they are of interest to somebody,
too.

  • special characters in queue names

Ticket #?

#7679

  • Unknown field: Requestor.EmailAddress
  • Relogin necessary to see queue changes
  • ticket search reveals higher total number of found tickets than allowed
    to see

There’s a patch for the first.

Ok, I see now. I checked the list before I reported the error, but back then
there was nothing mentioned.

The second two are design
artifacts.

Which means it can’t/won’t be fixed?

The third one, I know I’ve responded in depth to several
tickets about why a good solution is hard and expensive
(computationally).

Ok. I’ll see whether we can live with that kind of information leakage.

Cheers,
Stephan

inubit AG
integrating your business and IT
Tel +49.30.726112-300, Fax -100
http://www.inubit.com/su/public_key