Anonymous | Login

Project:

News | My View | View Issues | Roadmap | Summary

View Issue Details[ Jump to Notes ]

[ Issue History ] [ Print ]

ID

0027413

Type

Category

Severity

Reproducibility

Date Submitted

Last Update

defect

[Retail Modules] Web POS

major

always

2014-08-22 09:16

2016-05-25 12:33

Reporter

Orekaria

View Status

public

Assigned To

Retail

Priority

normal

Resolution

open

Fixed in Version

Status

new

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

0027413: Stabilization: It should never ever be necessary to clear cache.

Description

This is the most breaking action a user can perform to retail

- When this action is performed because the application stopped worked, then we have a critical issue

Note: This action is, at the same time, the best action to verify that the application recreates all the required user data (business partners, current cashup data, etc)

If the WebPOS reach the point of no need for clear cache, it would be a big step in the stabilization

Steps To Reproduce

NA

Proposed Solution

At the same time that logic must be added to allow this operation, we should inform the teams that any need of clearing cache, because the application stopped working properly and a simple refresh didn't work (not because the user just like it), should create a critical issue.

Tags

No tags attached.

Relationships [ Relation Graph ] [ Dependency Graph ]

related to	defect	0026589		closed	Orekaria	Stabilization: When the backend generates a new uuid.js, chrome does not update/delete the Web SQL database
depends on	feature request	0027329		new	Retail	Stabilization: Overhaul the loading process (since the url is entered until the webpos has loaded)
depends on	defect	0027380		closed	Orekaria	Stabilization: After log in, sometimes, the server is returning a 401: non authorized code
blocks	backport	0027431		closed	Retail	Sometimes the business partner is empty when the WebPOS loads
blocks	defect	0029396	RR15Q3	closed	Retail	Stabilization: RR15Q3 related
Not all the children of this issue are yet resolved or closed.

Notes
There are no notes attached to this issue.

Issue History
Date Modified	Username	Field	Change
2014-08-22 09:16	Orekaria	New Issue
2014-08-22 09:16	Orekaria	Assigned To	=> Orekaria
2014-08-22 09:16	Orekaria	Triggers an Emergency Pack	=> No
2014-08-22 09:17	Orekaria	Relationship added	blocks 0027329
2014-08-22 09:18	Orekaria	Relationship added	depends on 0027380
2014-08-22 09:29	Orekaria	Relationship added	related to 0027414
2014-08-22 09:30	Orekaria	Relationship added	related to 0026589
2014-08-22 09:47	Orekaria	Summary	Stabilization: It should never ever be necessary to clear cache => Stabilization: It should never ever be necessary to clear cache.
2014-08-22 09:47	Orekaria	Description Updated	View Revisions
2014-08-22 09:47	Orekaria	Relationship replaced	depends on 0027329
2014-08-29 10:59	Orekaria	Relationship added	blocks 0027431
2015-03-26 11:14	Orekaria	Relationship added	depends on 0029377
2015-03-27 12:57	Orekaria	Relationship added	blocks 0029396
2015-03-27 12:57	Orekaria	Relationship deleted	depends on 0029377
2015-05-15 17:47	marvintm	Severity	critical => major
2016-05-25 12:33	Orekaria	Assigned To	Orekaria => Retail

Copyright © 2000 - 2009 MantisBT Group