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.
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: