Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||||
| ID | |||||||||||
| 0006498 | |||||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||||
| feature request | [Openbravo ERP] B. User interface | minor | always | 2008-12-11 17:43 | 2008-12-19 16:47 | ||||||
| Reporter | rachelJohnston | View Status | public | ||||||||
| Assigned To | rgoris | ||||||||||
| Priority | normal | Resolution | open | Fixed in Version | |||||||
| Status | acknowledged | Fix in branch | Fixed in SCM revision | ||||||||
| Projection | none | ETA | none | Target Version | |||||||
| OS | Any | Database | Any | Java version | |||||||
| OS Version | Database version | Ant version | |||||||||
| Product Version | 2.50alpha-r3 | SCM revision | |||||||||
| Review Assigned To | |||||||||||
| Web browser | |||||||||||
| Modules | Core | ||||||||||
| Regression level | |||||||||||
| Regression date | |||||||||||
| Regression introduced in release | |||||||||||
| Regression introduced by commit | |||||||||||
| Triggers an Emergency Pack | No | ||||||||||
| Summary | 0006498: Bad terminology in Process Request window | ||||||||||
| Description | In General Setup > Process Scheduling > Process Request you can request system processes to either run immediately or at a later date. The Timing option controls the scheduling of the process and there are three options: immediately (self explanatory) later (process runs once at the time and date specified). scheduled (process runs recurrently at the date and time specified). If an end date and time is not specified the process runs indefinitely. IMO, the distinction between "Later" and "Scheduled" is difficult for the user to make, because if something is scheduled it is inherently later. The distinction is between a recurrent / ongoing task and a one off, discrete task. | ||||||||||
| Proposed Solution | The options could possibly be narrowed to 2: "Now" and "Scheduled" with appropriate dimming logic to help the user choose between the recurrent task or the one-off. Alternatively the labels could be changed to something like "Immediately" "Scheduled one-time" "Scheduled recurrent" | ||||||||||
| Tags | No tags attached. | ||||||||||
| Attached Files | |||||||||||
 Relationships [ Relation Graph ]
[ Dependency Graph ]
|
||||||||
|
||||||||
 Relationships |
|
Notes |
|
|
(0011613) rgoris (developer) 2008-12-19 16:46 |
Confusing indeed. I think renaming the labels as you propose, removes this confusion: "Immediately" "Scheduled one-time" "Scheduled recurrent" |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2008-12-11 17:43 | rachelJohnston | New Issue | |
| 2008-12-11 17:43 | rachelJohnston | Assigned To | => rgoris |
| 2008-12-11 17:43 | rachelJohnston | sf_bug_id | 0 => 2417647 |
| 2008-12-11 17:43 | rachelJohnston | Regression testing | => No |
| 2008-12-19 16:46 | rgoris | Note Added: 0011613 | |
| 2008-12-19 16:46 | rgoris | Status | new => acknowledged |
| 2008-12-19 16:47 | rgoris | Relationship added | blocks 0000504 |
|
Issue History |
| Copyright © 2000 - 2009 MantisBT Group |
 |