Vote #64407
完了Administration > Custom fields (list) > Possible values should be a textarea
0%
説明
The current way of filling in possible values of a list custom field is nice, but a simple textarea would actually be better.
Possible values would be listed as values separated by a linebreak.
Benefits:
- It would be much easier to reorder values. With the current multiple input, it's a tricky game...
- It would also be much easier to "clone" a custom field. For example, if a custom field contains the main parts of a website (only one project), it would be handy to be able to copy-paste these values to a new custom field for another similar project, where they only need to be changed marginally.
- It would be easier to "import" field values from other bugtrackers. Just copy and paste!
By the way, this way of entering multiple values with a textarea could be applied to other new features: adding multiple users or multiple issues at once, for instance.
What do you think?
journals
+2 :-)
FogBugz made a huge noise about their feature where you can enter issues as fast as you can type them and hit enter due to some clever Ajax, but all you really need is a text area.
More than custom fields, more than multiple users, the killer application here is adding a bunch of issues in one hit.
Think how often issues come in the form of emails, meeting notes, spec documents ect with a bullet pointed list of action items. What you want to be able to do is to paste that list into a text area, set some attributes that would apply to all of them and hit enter.
We had this on our previous (home grown) tracker and it encouraged splitting tasks down into much more fine grained tasks, which is usually a good thing, and saved much time and frustration.
--------------------------------------------------------------------------------
Thanks Ewan.
Could you change the title of this issue to make it more general? I'm not a native English speaker and it wouldn't be as effective if I do it.
Something like "Enter multiple items in a textarea (issues, users, custom field values...)"
--------------------------------------------------------------------------------
Or maybe the textarea can be an option to fill in initial list. The rest of behaviour can keep current implementation (IMHO it's better due to DB model).
--------------------------------------------------------------------------------
> The current way of filling in possible values of a list custom field is nice, but a simple textarea would actually be better.
Agreed. Change committed in r2267.
> Could you change the title of this issue to make it more general?
No. I dislike general feature requests.
But Ewan is right, being able to create a bunch of issues in one hit would be nice.
It shouldn't be that hard to do but I really prefer to see separate feature request.
> The rest of behaviour can keep current implementation
I don't see any good reason for keeping the prior behaviour.
A textarea is much more convenient to create or to maintain the value list. And no need for javascript :-)
--------------------------------------------------------------------------------