Project:
View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||
ID | ||||||||
0044065 | ||||||||
Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||
defect | [Retail Modules] Web POS | major | always | 2020-05-14 13:44 | 2021-08-23 09:26 | |||
Reporter | nicolasuriz | View Status | public | |||||
Assigned To | nicolasuriz | |||||||
Priority | high | Resolution | invalid | 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 | |||||||
Review Assigned To | ||||||||
Regression level | ||||||||
Regression date | ||||||||
Regression introduced in release | ||||||||
Regression introduced by commit | ||||||||
Triggers an Emergency Pack | No | |||||||
Summary | 0044065: It is not possible to add the Search Key of a preference in a message for the user in WebPOS | |||||||
Description | It is not possible to add the Search Key of a preference in a message for the user in WebPOS. So whenever the message tries to send some info to the user, the message is not clear for him/her so they cannot understand what is wrong. | |||||||
Steps To Reproduce | 1. Force a popup in WebPOS with some information related to a preference. | |||||||
Proposed Solution | The freedom to be able to add the search key of preferences to messages. | |||||||
Tags | No tags attached. | |||||||
Attached Files | ||||||||
Relationships [ Relation Graph ] [ Dependency Graph ] | |
Notes | |
(0120115) marvintm (manager) 2020-05-21 10:16 |
Sorry, but with the information provided we have not been able to understand the problem. Could you please provide more information, maybe some functional requirement you are trying to fulfil, or some code snippet of what you are trying to do and doesn't currently work? |
(0131253) marvintm (manager) 2021-08-23 09:26 |
We haven't been able to reproduce the issue, and we didn't get any clarification on it |
Issue History | |||
Date Modified | Username | Field | Change |
2020-05-14 13:44 | nicolasuriz | New Issue | |
2020-05-14 13:44 | nicolasuriz | Assigned To | => Retail |
2020-05-14 13:44 | nicolasuriz | Resolution time | => 1592517600 |
2020-05-14 13:44 | nicolasuriz | Triggers an Emergency Pack | => No |
2020-05-15 14:08 | nicolasuriz | Resolution time | 1592517600 => 1590616800 |
2020-05-15 14:08 | nicolasuriz | Type | design defect => defect |
2020-05-21 09:24 | prakashmurugesan88 | Assigned To | Retail => prakashmurugesan88 |
2020-05-21 09:24 | prakashmurugesan88 | Status | new => scheduled |
2020-05-21 10:16 | marvintm | Note Added: 0120115 | |
2020-05-21 10:16 | marvintm | Assigned To | prakashmurugesan88 => nicolasuriz |
2020-05-21 10:16 | marvintm | Status | scheduled => feedback |
2021-08-23 09:26 | marvintm | Note Added: 0131253 | |
2021-08-23 09:26 | marvintm | Status | feedback => closed |
2021-08-23 09:26 | marvintm | Resolution | open => invalid |
Copyright © 2000 - 2009 MantisBT Group |