search

kwekke / pe

0 stars 0 forks source link

Deleted projection #5

Open kwekke opened 4 years ago

kwekke commented 4 years ago

1) create 5 transactions of same category "cat" 2) add another transaction of no category 3) create projection of said category "cat" 4) update t6 c/cat updates the category of 6th transaction to be "cat" and then the projection created in step 3 is deleted. Although the UG says that Projection does not have the update function, it did not say that it would be deleted after such changes.

nus-pe-bot commented 4 years ago

Team's Response

Hey, first of all, thank you for your feedback.

To start, I've changed the tag of this issue to FunctionalityBug since the projection, having met the minimum number of transactions (= 5, as detailed in the UG) should be retained regardless of whether t6 is successfully updated.

I've also tagged my response as CannotReproduce as I have tried to reproduce the issue as follows:

Steps 1 & 2: Add 5 transactions with category cat and an additional GENERAL transaction image.png

Step 3: Cast a projection, I've also pulled up the projection graph for reference using the display command image.png image.png

Step 4: update t6 c/cat image.png

Thereafter, displaying the projection graph again, we see that an additional point has been added, which denotes t6 (x = -1, y = 60) image.png

(Going beyond simply trying to reproduce the issue...)

One possible reason why the projection was deleted when you were testing the app is because between step 3 and 4, the projection graph window was left open (i.e. after calling display p[x], update t6 c/cat was called before closing the projection graph). This is a documented feature of the projection graph, detailed in the UG (section 4.7.3 - Display command > Usage Constraints > Static Graph Rendering). For your reference, I've attached a screenshot of the relevant section here:

image.png

I hope this addresses the issue you raised adequately, and thank you once again for your feedback :)

Items for the Tester to Verify

:question: Issue response

Team chose [response.CannotReproduce]

Reason for disagreement: [replace this with your reason]

:question: Issue type

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

Reason for disagreement: [replace this with your reason]