Note from the teaching team: This bug was reported during the Part II (Evaluating Documents) stage of the PE. You may reject this bug if it is not related to the quality of documentation.
As per the title. I would like to consider this as quite a major bug as ALL data in the application will be lost without any prompt by the app, and I believe this import step is irreversible too.
As this is a HR management app, losing all the previous data without warning or a prompt could potentially be disastrous, as all employee data will be lost. I wanted to classify this as a feature flaw initially, since import is only useful if it 'adds on' instead of 'replace' for such a use case, however, I felt that you might have reasons for making a design decision to implement it as such. Thus I classified this under Documentation Bug instead.
Overall, I would propose that this is a medium severity bug either way.
Note from the teaching team: This bug was reported during the Part II (Evaluating Documents) stage of the PE. You may reject this bug if it is not related to the quality of documentation.
As per the title. I would like to consider this as quite a major bug as ALL data in the application will be lost without any prompt by the app, and I believe this import step is irreversible too.
As this is a HR management app, losing all the previous data without warning or a prompt could potentially be disastrous, as all employee data will be lost. I wanted to classify this as a feature flaw initially, since import is only useful if it 'adds on' instead of 'replace' for such a use case, however, I felt that you might have reasons for making a design decision to implement it as such. Thus I classified this under Documentation Bug instead.
Overall, I would propose that this is a medium severity bug either way.
Screenshot of the UG for reference:
[original: nus-cs2103-AY2122S1/pe-interim#5150] [original labels: severity.Medium type.DocumentationBug]