New Requirement or Test and Behavior of Undo Checkout

Tags:

Question ID: 107069

We have an end user that performs the following actions:

1. In a version controlled project, create a new requirement or test. Just enter required information and submit.
2. Do not check in the test/requirement. Instead, perform an "Undo Checkout".

The user’s expectation is that the requirement/test should be deleted considering the initial version was not checked in.

This behavior has been around awhile, so I’m sure the requirement/test is not deleted for a specific reason,

Marked as spam

Posted by gobroncos (Questions: 193, Answers: 14)

Asked on August 18, 2016 8:11 pm

29 views

Answers (1)

▲

▼

✔

Private answer

Based on basic DB/record knowledge of QC is that when creating a NEW record in QC, the user fills in various fields and saves/submits/clicks ''next'' etc.
The record has been saved in the DB by this point, and check-out/undo check-out is irrelevant to record deletion.

Once you click SUBMIT, the record gets stored in the database (History - version ''1'') and is immediately checked-out to the creating user.
This is the ''initial'' version, version control has to start somewhere.

This is working as designed for a version controlled project.

Marked as spam