Open yhtingg opened 4 years ago
This is due to the user editing the configuration file, which is not a supported use case stated in the current User Guide. Hence, this bug is out of scope.
In the future, only if we decide to support relocation of data files, we will clarify that the paths should be readable/writable by the user, but this does not apply to the current version.
Team chose [response.Rejected
]
Reason for disagreement: Unfortunately, I did not edit the configuration file as hypothesised by the team. The error could have occurred due to the default file path set by the team being a protected path in my computer. However, such settings may differ from computer to computer.
Perhaps a more commonly unprotected file path would be more suitable to be the default one.
Team chose [severity.Low
].
Originally [severity.High
].
Reason for disagreement: [replace this with your reason]
Team chose [type.DocumentationBug
].
Originally [type.FeatureFlaw
].
Reason for disagreement: I still feel that it is a feature flaw as it makes the app unusable to some users who have some of their filepaths protected as the data is unable to be saved, nor can they change the filepath of their data file.
Unable to save state