View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0005838 | mantisbt | bugtracker | public | 2005-06-24 04:40 | 2020-08-09 07:53 |
Reporter | polzin | Assigned To | atrol | ||
Priority | normal | Severity | text | Reproducibility | N/A |
Status | closed | Resolution | no change required | ||
Product Version | 1.0.0a3 | ||||
Summary | 0005838: text suggestions: Update->Edit/Change, Advanced->Extended, Apply Filter/Use Filter ambigouity | ||||
Description | I changed several texts in my custom_strings.php and thought, perhaps someone else might be interested. Users were confused with the "Update" buttons. Though I am not a native speaker, I believe that with pressing "update", one would expect the program to update the displayed information (e.g. rereading from the database in case it has changed). $s_actiongroup_menu_update_priority = 'Change Priority'; Additionally, I think "Extended" is more appropriate than "Advanced", but this will be a matter of taste. Thirdly, in the filters of view_all_bugs_page there is a "Apply Filter" and a "Use Filter" button. I believe that it´s a little confusing, because the names are not the same, but do not really make a difference (you could swap them). One possibility to solve this minor ambigouity would be to eliminate the "Use Filter" button, if javascript is turned on. (And to be consistent also the "Switch" button near the project selection drop-down). | ||||
Tags | No tags attached. | ||||
part 1 is a duplicate of 0004816 |
|
Reminder sent to: siebrand What are your thoughts on this for 1.3? I tend to agree that "update" is not the best word to be using. "change" is not a bad alternative. Otherwise, "modify" or "edit" could be used. I'm sure there are other options too. |
|
With 2.0 this is obsolete and can be closed. |
|