I understand JFS supports only custom fields but not built-in fields (like affected version, fixed version, priority, etc).
How to cope with this serious limitation?
The only possible solution could be to define custom fields for each built-in field (and to maintain the values equal between these fields), but I do not like this kind of solution.
Any idea?
Thanks,
Gaby
Hi Gaby,
Actually your solution with custom fields is the only one possible for the time being. But JFS 2.0 is under development right now and it'll definitely will support more built-in fields.
Alex
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.