Roundup Tracker - Issues

Issue 621795

classification
Allowing semi-colon as item separator
Type: rfe Severity: normal
Components: Interface Versions:
process
Status: closed wont fix
:
: richard : jkew, richard
Priority: normal :

Created on 2002-10-11 10:03 by jkew, last changed 2002-10-28 10:40 by jkew.

Messages
msg3079 Author: [hidden] (jkew) Date: 2002-10-11 10:03
I often trip myself up by using semi-colons instead of commas when 
entering multi-item nosy lists in the web interface -- a muscle 
memory imposed by our use of Outlook for email, which insists on 
semi-colons to separate multiple email 
recipients.

Allowing both semi-colons and commas as 
separators -- and transparently converting semi-colons to commas 
on input -- would be kinder to Windows-based idiots like me.
msg3080 Author: [hidden] (richard) Date: 2002-10-11 10:17
Logged In: YES 
user_id=6405

The only problem with this is that currently the comma-separated list 
is standard across all three user interfaces. The mail gateway 
specicially uses semicolons for separating arguments in its extended 
subject line syntax (ie. [assignedto=richard; status=open]) 
 
I worry that it might be confusing and that people would attempt to 
use semicolons in the subject line where they mean to use commas...  
 
msg3081 Author: [hidden] (jkew) Date: 2002-10-28 10:40
Logged In: YES 
user_id=598066

Ah, OK -- I hadn't realised that semi-colons already had meaning in the 
email interface. I'll have a read of its documentation before making any 
more web-interface suggestions. (We don't run the email interface so I'm 
not familiar with it; getting it up and running is on my to-do list.)

I 
seem to have got into the comma habit now anyway...
History
Date User Action Args
2002-10-11 10:03:35jkewcreate