search

glenn-chew / pe

0 stars 0 forks source link

Updating a header to an existing header #8

Open glenn-chew opened 3 days ago

glenn-chew commented 3 days ago

Description, If the new header has a name that already exists in the table, then the update still continues resulting in a duplicate in the header names. It also copies all the data over, but the data no longer has the same type as the header.

image.png

nus-pe-script commented 11 hours ago

[IMPORTANT!: Please do not edit or reply to this comment using the GitHub UI. You can respond to it using CATcher during the next phase of the PE]

Team's Response

Our team acknowledges the issue which affects both data integrity and user experience in a significant ways and would work towards rectifying this issue in future increments of the project. The severity should remain as "Medium"

However, our team feel strongly against it being a "FunctionalityBug" since the root cause of this issue would learn more towards design oversight in enforcing unique header names during updates. This makes the issue more of a feature implementation flaw rather than a core functionality failure; thus assigning the bug type to be "FeatureFlaw" instead.

Items for the Tester to Verify

:question: Issue type

Team chose [type.FeatureFlaw] Originally [type.FunctionalityBug]

Reason for disagreement: [replace this with your reason]