Project:
View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||
ID | ||||||||
0057475 | ||||||||
Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||
defect | [Openbravo ERP] 01. General setup | trivial | always | 2024-12-17 15:37 | 2025-01-07 20:36 | |||
Reporter | philippe_mui | View Status | public | |||||
Assigned To | philippe_mui | |||||||
Priority | low | Resolution | no change required | Fixed in Version | ||||
Status | closed | 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 | SCM revision | |||||||
Merge Request Status | ||||||||
Review Assigned To | AugustoMauch | |||||||
OBNetwork customer | Gold | |||||||
Web browser | ||||||||
Modules | Core | |||||||
Support ticket | ||||||||
Regression level | ||||||||
Regression date | ||||||||
Regression introduced in release | ||||||||
Regression introduced by commit | ||||||||
Triggers an Emergency Pack | No | |||||||
Summary | 0057475: RM-19821 Empty display in the "Timing on Process Request" dropdown list | |||||||
Description | In Process request window, there is an empty line in Timing field https://openbravo.atlassian.net/browse/RM-19821 [^] | |||||||
Steps To Reproduce | In Process request window Open any process request or create a new one In Timing field, click to display the dropdown list Current result: An empty line is displayed in the dropdown list Expected result : no empty line is displayed and only 'Run immediately, Run later and Schedule are displayed | |||||||
Tags | FASH | |||||||
Attached Files | ![]() | |||||||
![]() |
|
![]() |
|
(0173727) AugustoMauch (administrator) 2024-12-30 10:39 |
Hello Philippe, If the field is left empty, the behavior is the same as when the "Run Immediately" option is selected. Because this has been always working like this, I would rather not to change the behaviour. It is possible that existing clients have some entries where the Timing field is empty, and enforcing now to make it not-nullable would be an API change. I don't think the change is worth it for a trivial issue. |
(0173878) philippe_mui (viewer) 2025-01-07 20:34 |
Ok, thanks. We can close this ticket |
![]() |
|||
Date Modified | Username | Field | Change |
2024-12-17 15:37 | philippe_mui | New Issue | |
2024-12-17 15:37 | philippe_mui | Assigned To | => Triage Omni OMS |
2024-12-17 15:37 | philippe_mui | File Added: Screenshot 2024-12-17 153024.png | |
2024-12-17 15:37 | philippe_mui | OBNetwork customer | => Gold |
2024-12-17 15:37 | philippe_mui | Modules | => Core |
2024-12-17 15:37 | philippe_mui | Triggers an Emergency Pack | => No |
2024-12-17 15:37 | philippe_mui | Tag Attached: FASH | |
2024-12-17 16:21 | aferraz | Assigned To | Triage Omni OMS => Triage Platform Base |
2024-12-30 10:39 | AugustoMauch | Note Added: 0173727 | |
2024-12-30 10:39 | AugustoMauch | Assigned To | Triage Platform Base => philippe_mui |
2024-12-30 10:39 | AugustoMauch | Status | new => feedback |
2025-01-07 20:34 | philippe_mui | Note Added: 0173878 | |
2025-01-07 20:36 | philippe_mui | Review Assigned To | => AugustoMauch |
2025-01-07 20:36 | philippe_mui | Status | feedback => closed |
2025-01-07 20:36 | philippe_mui | Resolution | open => no change required |
Copyright © 2000 - 2009 MantisBT Group |