World: r3wp

Works like a charm !

right, works now.

index.rsp doesn't work !

(Accueil link)

let me see that...

works here

right, works only when Projects selector is set to "all"

There's a bug in %index.rsp from a change I did last week in the 
statistics SQL code. Fixing...

Fixed

Should work ok now.

The "Attached Files" zone in ticket edition mode is not yet working 
so just ignore it.

ok. Must go. See later

If someone can do a step by step blow on installing curecode ( including 
what ever one has to do with mysql ) .. I will try and set it up 
as well .. I need a public bug tracking database too.

Several questions:


- what is meant by Severity field of values - text, block, feature? 
I do understand major, minor, trivial, etc., but not those mentioned 
...

- for better searches, I would expect field 'fields to be filled 
in with every field form contains. E.g. I want to filter using 'Built-in

- CureCode, if slightly refined, could serve as auto changelog generation 
system. But Carl (or responsible person) would have to fill-in 'built-in 
field. In the past, I e.g. proposed addition of small table called 
Releases to RAMBO for such purposes. It would contain named releases. 
Main base could have small helper, value 'next pre-filling 'buil-tin, 
once someone markes it as built. 'next would be related to the closest 
relese from the Releases table.

Severity:
- Text: typo error, wrong text,...(minor severity)
- Block: blocking issue or error (worst severity with Crash)

- Feature: not really a bug, more a new feature (it has been almost 
superceded by the new Type field)


Searches: the search feature currently only works on TEXT fields 
(missing 'comments field). Version, built-in and others are INTEGER 
fields storing ID they should be in the filter section. The filter 
section needs to be expanded.


Changelog: it seems to me more reliable and secure to just correctly 
fill-in the 'built-in field once built.

re Block - ah, I thought it is related to REBOL block! datatype :-)

I thought these were interesting priority codes http://simile.mit.edu/wiki/Priority_Codes

I think that explicit words are easier to remember than P1,P2,P3...

I mentioned it not so much for the codes, but the classes they use 
.. eg P9

I saw the classes but in CC (and in all other trackers I worked with) 
priority is not the key property driving the workflow, the most important 
one is : status. In CC/R3, P9 class would have the status "dismissed".

Anyway in CC, you can define your own list of priorities, statuses 
and severities if the default ones don't suit your needs.

Is CC for R3 closed for new users?

No, it's not and was never planned to be.

Looks like Paul had some difficulties registering or maybe hit a 
bug. In this last case, I'd like to see a detailed report (in this 
channel) from Paul.

Reports back "error account not yet activated".

I tried to register again and get this "Sorry, this page cannot be 
displayed. Try again or contact the web site administrator."

Steeve had similar problems - that is why we had to request that 
you add an account, Doc.

Error account no yet activated

 => check your junk folder in your mailbox for the confirmation email 
 (I need to investiguate on this one, could be caused by different 
 kind of issues)

Don't worry about getting me an account for curecode.  I'm not on 
the team that is working on R3.  Henrik was just trying to allow 
me to submit an enhancement throu there.

I'll check it - hold on.

nope nothing there related.

Sorry...

 message => trapped RSP script error, I'll look in the log file to 
 see what caused that.

Ok, so either your mail server didn't accepted emails from CureCode 
server, or there's a random bug on CureCode's email sending script.

Anyway thanks for the info Paul.

I don't know why my mail server would deny it.  I can try a different 
email account though.

Please do. I'll force activation on your first account.

Let me know when ready as it says that account exists.

Your first created account is active now.

Yep that worked.

You provided the same email address in the second attempt.

Yep.  No problem its working.

Doc, curecode site is nice and fast - good work!

I have lost some work on occasion due to the login timeout not being 
long enough. The post-only interaction model means that I can't go 
back to get my edits, so if I have to log in again my edits are lost 
for good.

I have taken to composing my comments and tickets offline as a result.

either have a longer timeout or implement ajax pings to keep session 
active

Brian, I agree that's an issue that needs to be solved. I thought 
about removing session timeout. Session would then end only when 
the browser is closed.

On second thought, that solution wouldn't be reliable enough on server 
side.

Not even that. It would be sufficient to do two things:

- Do a server-side redirect to a get page when you go into edit mode 
on a ticket or comment update.

- If doing a post and the session has timed out, create a new session 
and save the data to it temporarily and take the person to a login 
page. After the relogin, take them back to the page with their edits 
prefilled in. Then let them save (or perhaps save on the way).

Yes, that would be a good approach that could solve the issue at 
application level (not having to modify Cheyenne's session framework).

That is the method I used when I ran into this situation in the past 
with ASP.NET and ColdFusion sites - don't know the RSP version.