search

chongjunwei / pe

0 stars 0 forks source link

Assignments disappear after the following sequence #7

Open chongjunwei opened 2 years ago

chongjunwei commented 2 years ago

Start from default config of the app

  1. view asg

Screenshot 2021-11-12 at 4.51.34 PM.png

  1. cd CS2103

Screenshot 2021-11-12 at 4.51.50 PM.png

  1. mkasg n/Side quest 10 w/20 s/50

Screenshot 2021-11-12 at 4.52.02 PM.png

  1. view asg

Screenshot 2021-11-12 at 4.52.14 PM.png

Now, if I try to go to view contacts then toggle back to view asg, the assignments still don't show up.

cd * does not work as well.

The assignments for all modules only reappear after I close the app and open it again, and then enter the view asg command. However, when I try "cd CS2103", a blank screen appears.

nus-pe-bot commented 2 years ago

Team's Response

Duplicate of #4296. Expected behaviour should be a table of assignments with details (id, name, score, status etc.)

The 'Original' Bug

[The team marked this bug as a duplicate of the following bug]

Unable to display assignments

Step to reproduce

  1. mkmod cs2100
  2. cd cs2100
  3. mkasg n/test asg w/10 s/100
  4. view asg

Expected behaviour: The assignment list is displayed

Actual behaviour

image.png

However, the assignment is actually created since dlasg still works. Steps to reproduce (follow up from above):

  1. mkasg n/haha w/80 s/100 (assignment name is random pls don't take it seriously)
  2. view asg (still empty screen)
  3. dlasg 2

image.png

I choose this as severity High since the user cannot know what assignments are already in the system and have to memmorise themselves to use the app.

[original: nus-cs2103-AY2122S1/pe-interim#4240] [original labels: type.FunctionalityBug severity.High]

Their Response to the 'Original' Bug

[This is the team's response to the above 'original' bug]

Accepted as a high functionality bug.

This was a very major regression introduced by a last minute PR. The expected behaviour is a table showing the assignment info, such as ID and names.

Items for the Tester to Verify

:question: Issue duplicate status

Team chose to mark this issue as a duplicate of another issue (as explained in the Team's response above)

Reason for disagreement: [replace this with your explanation]

:question: Issue severity

Team chose [severity.High] Originally [severity.Medium]

Reason for disagreement: [replace this with your explanation]