com_job cannot be done through Index

[wpx12011]

com_job and uncom_job cannot be done by specifying the job index, while edit_job can. It's easier to find the job by the index than keying / copying the job id.

[nus-pe-script]

Team's Response

For convenience, user can copy paste the job ID and that's why we did not include com_job/uncom_job by index

Items for the Tester to Verify

❓ Issue response

Team chose [response.NotInScope]

• I disagree

Reason for disagreement:

I do not agree with the reclassification from FeatureFlaw to NotInScope. I think this problem is within scope as referring jobs by their indexes is implemented in command edit_job. It is very inconsistent that among all job-related commands, some can refer the target job by its index while the rest cannot.

Moreover, the team argues that "For convenience, user can copy paste the job ID and that's why we did not include com_job/uncom_job by index", I think that it is intuitive that referring to a job by its index is more convenient. Below is a list of description of user's actions under 2 scenarios.

(A) Indexing a job by its job ID:

1. scroll through the job list to find the job
2. move your mouse over it
3. select the job (need to click on the job box and see the job box highlighted in blue)
4. press ctrl-c
5. move you mouse back to the command box
6. click the command box at the position where you want to insert the job ID
7. ctrl-d to paste job ID

(B) Indexing a job by its index in job list:

1. scroll through the job list to find its index
2. key in the index in the command box
   (no need for any mouse-clicking)

Through the comparison, we can see that indexing a job by its job ID is very troublesome, involves a lot of clicking and depends heavily on the GUI interface (must interact with the GUI by clicking on the job to select it before copying job ID), while indexing a job through its index is much easier.

In conclusion, I insist my view that unable to refer to a job by its index in the job list in this command is a Feature Flaw. Since it is 1). inconsistent with other commands. 2). depends too much on GUI interactions, which is counted against the product design aspect of the project.

---

❓ Issue severity

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

• I disagree

Reason for disagreement: I disagree with the reclassification of severity from Medium to Low. I think that the issue should have severity.Medium since it could cause occasional inconvenience.

Delivery job status is an important feature in this application. I think that for a normal usage of this application, each job need to be update its completion status for at least once. It is not a rare occasion so cannot be classified as severity.Low.

Furthermore, each time we update the job status we need to experience this inconvenient process:

Indexing a job by its job ID:

1. scroll through the job list to find the job
2. move your mouse over it
3. select the job (need to click on the job box and see the job box highlighted in blue)
4. press ctrl-c
5. move you mouse back to the command box
6. click the command box at the position where you want to insert the job ID
7. ctrl-d to paste job ID

I think it causes some inconvenience to the user thus severity.Medium is more appropriate.

---