Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0052792
TypeCategorySeverityReproducibilityDate SubmittedLast Update
feature request[POS2] POSmajoralways2023-06-20 12:482024-06-19 15:13
ReporternicolasurizView Statuspublic 
Assigned ToRetail 
PriorityhighResolutionopenFixed in Version
StatusscheduledFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Review Assigned To
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0052792: When a Verified Return reason it is added, it is not displayed at lines level even though it was selected.

DescriptionWhen adding a verified Return Reason :

The reason that is selected by the user is not displayed below the product name in the ticket.
Whereas, When a line is returned directly in the line of the ticket the reason is displayed
Steps To ReproduceJira associated with a video in livebuilds included:
https://openbravo.atlassian.net/browse/GIFI-200 [^]
https://drive.google.com/file/d/1Kvrk3XKZMkbmmtzFYLSj_nsuliVGb8As/view [^]

1.For the Role “vallblanca store” : SETUP the user action “Verifed Return Ticket” to have a reason to set (with an approval)
2.Fill at least one reason for the user action ““Verifed Return Ticket””
3.Create a “verified return” and set a reason
4.The reason is not displayed below the name of the product
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]

-  Notes
(0151760)
marvintm (manager)
2023-06-28 16:03

Reasons in React currently do not work like this. It is a generic feature which can be used for all user actions, which is nice, but due to that, we would have problems showing them in the Order component, as they could be associated with many different actions.

A feature request should be raised to Product Management and discussed with platform team. Maybe a possible approach would be to be able to programmatically "flag" specific user actions, so that if reasons are provided for them, they are shown in the order component.

- Issue History
Date Modified Username Field Change
2023-06-20 12:48 nicolasuriz New Issue
2023-06-20 12:48 nicolasuriz Assigned To => Retail
2023-06-20 12:48 nicolasuriz Triggers an Emergency Pack => No
2023-06-20 12:49 nicolasuriz Steps to Reproduce Updated View Revisions
2023-06-28 12:17 sreehari Assigned To Retail => sreehari
2023-06-28 13:03 sreehari Status new => scheduled
2023-06-28 14:24 kchoperena Steps to Reproduce Updated View Revisions
2023-06-28 16:03 marvintm Note Added: 0151760
2023-06-28 16:03 marvintm Type defect => feature request
2024-06-19 15:13 sreehari Assigned To sreehari => Retail


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker