World: r3wp

Robert, I use curecode on my Linode. It took about a day to set up 
due to numerous little things, but I can probably help.

1 day... wow. I just thought: Install RSP, call init page, fill-in 
some informaiton. Done. Ok... will think about it.

it's likely that many of those bugs are fixed in 0.9.9. I'm running 
0.9.8. one big problem was to find a rebol version that would run 
on my server, in combination wtih curecode 0.9.8. I decided to go 
for a slightly older version to make that combination easier.

some fixes in curecode also require fixes in cheyenne, etc.

I have a dumb idea: Why not extend Curecode with a client package? 
The client package would be integrated into a program. When a crash 
occurs in your program, a bug report could be sent directly to your 
curecode database. There would be a distinction necessary to identify 
similar reports and gather them under one report.

Good idea. IMO the distinction is to hard to too. Better to add a 
curecode admin function to merge tickets but keep the ticket ID towards 
the customers.

Henrik: I'm doing that for one of our REBOL-based commercial product, 
but sending crash reports to dedicated database table. Creating tickets 
directly could be done without much efforts, but I would avoid mixing 
those automated reports with hand-written ones. Interesting idea 
to think about anyway.

Is there any way how to get code formated in some more readable way 
(at least inside "Example code" field)?

Yes, I could change the font to a monospace one.

Maybe just wrapping the code in <PRE> tag would be enough, didn't 
tested that yet.

I've made a small improvement in the rendering of the "Example code" 
field in view mode (edit mode is unaffected). Let me  know if it's 
better now.

Oldes, I think that you can now remove the <pre> tags from code part 
in ticket  #1369.

Henrik, you can probably identify the crash by the error object and 
then create a checksum from it to avoid duplicates.

My product collects error objects and sends them to my gmail account 
with optional comments from users.  But they're usually easy to fix 
so not worth entering into a database.

And to avoid issues with asking users to setup the smtp details, 
I hard code gmail's smtp server :)

yes, that might be possible.

I'd like to hear your opinion about ticket #1371 where Meijeru is 
asking for ticket submitters to be granted the right to delete their 
own tickets ("Developer" and "Admin" users can delete any ticket). 
This right has been restricted to "Reporter" users to avoid situations 
where comments added by other users, having valuable information 
would risk to be lost due to intentional or unintentional deletion 
by the ticket's owner. Maybe this policy is too restrictive as pointed 
out by Meijeru. What do you think?

agree until the ticket is "touched" by someone else.

So only while the ticket's status remains "submitted" and no comment 
has been added by other users, the owner can delete it. Seems ok 
to me.

I agree with Steeve.

Sounds like a good policy to me.

I agree also.

Looks like there's a consensus. I have a few improvements pending 
for CureCode to be done this week, so I'll add also this new rule 
to my todo list.

Here's an old rule that just broke: A non-admin undismissed a ticket 
- their own ticket, but still. This should not be allowed.

Agreed.

I've just made a minor CureCode upgrade. Changes are :

FIX: Issue #1371 regarding policy for ticket deletion by owner.
FIX: Dimissed ticket can't be changed by the owner anymore.
FIX: Minor missing translations for french catalog.

Ticket #1371 status is now built, I'll close it in a few days after 
a few more tests in production.

Regarding the second fix I've made, a ticket with status "dismissed" 
won't allow its owner (if profil type is Reporter) to change it. 
The owner still can add comments to the dismissed ticket if needed.

As usual, let me know if you see any regression after this update.

Doc, why don't you expand curecode into a full ITIL package?

Use it to handle not just bug tracking but general IT support issues 
within the ITIL framework.

Other solutions like Remedy and HP Server Center (which I have used 
since before HP owned it) are not very good solutions.

There is a true void in that market that is being dominated currently 
by powerhouses just because of their perceived value not their actual 
value.

The gap between CureCode and solutions like Remedy is huge in terms 
of features. Trying to compete with them would require a large funding 
and a lot of time that I both lack.

Could make it an opensource project.

Doc could you activate my account in curecode please?

Pavel, your account is now active.

There was several accounts not activated, I've switched them all 
on. I guess that the activation email didn't make it (using an old 
extension of SEND mezz command). It's time to upgrade CC to the new 
builtin email support API and MTA...

THX

CureCode had a problem when I created my account a couple of days 
ago, went to a page not found, and didn't send me a notification 
mail.  After that it wouldn't let me try and sign up for that name 
again.  Reset password came up with an error page as well.

Your account has been validated, you can use it now. I got an error 
also while validating your account, this is new. I'll check the server 
to see what's going wrong.

Thanks, I'll have to reset the password, I was messing with errors 
and never wrote what I picked down...

Please wait a minute, I'm restarting the server.

Done.

Reset password is giving me "Sorry, this page cannot be displayed. 
Try again or contact the web site administrator." after I submit 
id and email address

Running to lunch now but will check in with it when I get back...

Hi Doc, one small thing... Chrome browser does not remember the login 
password cookie.

Hi Carl, I'll check that too.

Doc, we'll need a RAMBO migration to a new CureCode project some 
time next month, after the new R2 release. Open tickets only should 
be fine. Afaict we won't need to delay the first R2 release until 
the migration happens. The first release should be emergencies (like 
installation) and low-hanging fruit only.

No problem, we can add a new project to the current server when you 
need it.