Hi all,
I just wanted to report an issue or two and realized I did not have a
real user for it. Should I just use guest/guest or would it be better to
apply for a real account?
Also, is it really wise to keep the bug reporting & fixing stuff in an
instance that is used for testing, as well? I can see how it conveys the
trust you have in your product, but…
Richard
PS: I attached a screenshot of how RT 3.8.1 looks in Konqui. Kinda
weird 
Just send an email to rt-bugs@bestpractical.com and your account will be
created.2008/9/8 Richard Hartmann richih.mailinglist@gmail.com
Hi all,
I just wanted to report an issue or two and realized I did not have a
real user for it. Should I just use guest/guest or would it be better to
apply for a real account?Also, is it really wise to keep the bug reporting & fixing stuff in an
instance that is used for testing, as well? I can see how it conveys the
trust you have in your product, but…Richard
PS: I attached a screenshot of how RT 3.8.1 looks in Konqui. Kinda
weird
List info:
The rt-devel Archives
Hi all,
Hi,
I just wanted to report an issue or two and realized I did not have a
real user for it. Should I just use guest/guest or would it be better to
apply for a real account?
guest is enough, but easier … just send a mail to
rt-bugs@bestpractical.com 
Also, is it really wise to keep the bug reporting & fixing stuff in an
instance that is used for testing, as well? I can see how it conveys the
trust you have in your product, but…
+1
PS: I attached a screenshot of how RT 3.8.1 looks in Konqui. Kinda
weird
The way css is done in this part of the UI should really be rewriten I
think, I opened a bug report that talk on related problems:
http://rt3.fsck.com/Ticket/Display.html?id=10079
I already did some tests to fix this, but didn’t came into a nice
solution, I need to try it again when free time 
Thanks 
The way css is done in this part of the UI should really be rewriten I
think, I opened a bug report that talk on related problems:
I tried to make 12437 refer to it, but I got permission denied with the
guest user. Will try with my autogenerated one, later…
The way css is done in this part of the UI should really be rewriten I
think, I opened a bug report that talk on related problems:I tried to make 12437 refer to it, but I got permission denied with the
guest user. Will try with my autogenerated one, later…
I added the link, guest and unpriviledged users doesn’t have rights to
link to someone else ticket.
I added the link, guest and unpriviledged users doesn’t have rights to
link to someone else ticket.
Thanks. Is writing this mail the right way to apply for more rights
for my user so I
can do this myself, in the future?
Richard
You won’t get more rights. It’s not practical for BP to manage user
privileges for everyone.On Mon, Sep 8, 2008 at 11:34 AM, Richard Hartmann < richih.mailinglist@gmail.com> wrote:
On Mon, Sep 8, 2008 at 16:39, Emmanuel Lacour elacour@easter-eggs.com wrote:
I added the link, guest and unpriviledged users doesn’t have rights to
link to someone else ticket.Thanks. Is writing this mail the right way to apply for more rights
for my user so I
can do this myself, in the future?Richard
List info:
The rt-devel Archives
Also, is it really wise to keep the bug reporting & fixing stuff in an
instance that is used for testing, as well? I can see how it conveys
the
trust you have in your product, but…
We don’t use it for testing (other than the fact that we keep it
updated to a near bleeding-edge release of RT). However, there are
many folks on the net who think that it’s a great place to try
creating test tickets. The “Test” queue helps keep them from creating
bugs in RT complaining that the printer isn’t working.
-j
We don’t use it for testing (other than the fact that we keep it updated to
a near bleeding-edge release of RT). However, there are many folks on the
net who think that it’s a great place to try creating test tickets. The
“Test” queue helps keep them from creating bugs in RT complaining that the
printer isn’t working.
That’s what i meant with ‘used for testing’. Written in an ambigious way, sorry
for that. What I mean is why not seperate the playground RT from the bug
tracking RT? With a cron-driven auto-restore, you could give all guests admin
rights and they would be able to play & test even more.
Richard
That’s what i meant with ‘used for testing’. Written in an ambigious way, sorry
for that. What I mean is why not seperate the playground RT from the bug
tracking RT? With a cron-driven auto-restore, you could give all guests admin
rights and they would be able to play & test even more.
Be careful about that. “All admin rights” will let your users run
arbitrary code on your RT server.
We have such a demo server for potential customers, but not one we
currently share with the general public.
We have about 90% of such a server. We just have rather a lot to do
Be careful about that. “All admin rights” will let your users run
arbitrary code on your RT server.
Ouch, point noted. I won’t set up anything like that anyway, as there is no
use, to me. But it’s good to keep it in mind nonetheless.
We have such a demo server for potential customers, but not one we
currently share with the general public.
Understandably so.
We have about 90% of such a server. We just have rather a lot to do
Indeed. And you do it well, too
Richard
