generated from amosproj/amos202Xss0Y-projname
-
Notifications
You must be signed in to change notification settings - Fork 0
Bug Report
Kevin Nguyen edited this page Feb 8, 2023
·
3 revisions
The purpose of this page is to track the current bugs in the software. A detailed description of each bug can be found in the corresponding GitHub issue in the board.
The priority levels are sorted by severity from high to low:
- URGENT
- HIGH
- MEDIUM
- LOW
| Short description | Priority | Long description |
|---|---|---|
| Race conditions | URGENT | No optimistic locking has been implemented. For further information refer to https://github.com/amosproj/amos2022ws04-specitem-database/wiki/Race-conditions. |
| Non-UTF-8-characters might cause trouble when filtering SpecItems. | MEDIUM | Java, JavaScript and SQL have their own set of special characters which aren't identical. Using the UTF-8 character set is the lowest common denominator. Other characters will be handled as ? so that the user is filtering for ? instead of the intended character(s). |
| Unable to export the history of a SpecItem. | LOW | The data model of a SpecItem has changed and contains more information (columns/attributes/...) than the initial data model. The respecting export function hasn't been updated yet. |
| Version counter doesn’t work properly. | LOW | The version counter for a given SpecItem operates in a global scope. It increments if any newly created SpecItem is added to the database. Possible desired behaviour: every SpecItem should have their own version counter. |
| Uploading a file with commit information and SpecItems results in a 500 internal server error. | LOW |