|
List Info
Thread: Required fields in 2.1.0
|
|
| Required fields in 2.1.0 |
|
2007-03-13 04:38:41 |
Hello,
I don't know if I should report issues on the mailing list
or in the
sf.net tracker for the integration build. There won't be
many I think,
but here's one.
Custom field required even if already set:
1. Add a custom field (we have "Severity") to the
tracker, make it required.
2. Create an issue. Here you must enter a value for the
field.
3. Open the new issue and set to Closed.
4. Form validation (very nicely presented btw) says
"enter a value"
for the field. This is a bug, because it already has a value
in the
history, and I don't want to change it.
Of course this is tricky, because Comment is rightfully
mandatory for
every new log message. But compared to 2.0, with the custom
field only
mandatory on create, this is a usability issue.
/Staffan
------------------------------------------------------------
-------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the
chance to share your
opinions on IT & business topics through brief
surveys-and earn cash
http://www.techsay.com/default.
php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
j-trac-users mailing list
j-trac-users lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/j-trac-use
rs
|
|
| Re: Required fields in 2.1.0 |
|
2007-03-13 06:52:46 |
|
Thanks Staffan, don't bother raising a tracker for this, this needs to be fixed anyway.
It is worth mentioning that I'm planning to change the existing "E=Edit, V=View" system to "M=Mandatory, O=Optional, R=Read-Only" and therefore "unify" this across the New and Update screens. Also we need a way to flip a custom value from not-null to null - which interestingly is not possible today as far as I can remember...
And in a next release a "H=Hidden" also will be added. This will be some work, because of the need to hide the generated e-mail, hide in query results etc.
On 3/13/07,
JTrac users mailing-list < j-trac-userslists.sourceforge.net">j-trac-userslists.sourceforge.net> wrote:
Hello,
I don't know if I should report issues on the mailing list or in the
sf.net tracker for the integration build. There won't be many I think,
but here's one.
Custom field required even if already set:
1. Add a custom field (we have "Severity") to the tracker, make it required.
2. Create an issue. Here you must enter a value for the field.
3. Open the new issue and set to Closed.
4. Form validation (very nicely presented btw) says "enter a value";
for the field. This is a bug, because it already has a value in the
history, and I don't want to change it.
Of course this is tricky, because Comment is rightfully mandatory for
every new log message. But compared to 2.0, with the custom field only
mandatory on create, this is a usability issue.
/Staffan
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
j-trac-users mailing list
j-trac-userslists.sourceforge.net">j-trac-userslists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/j-trac-users
|
[1-2]
|
|
|
about | contact Other archives ( Real Estate discussion Medical topics )
|