P4DTI issue job000055

TitleRetrospective fixing violates workflow
Assigned userRichard Brooksby
DescriptionIn the UG we say that users can add fixes retrospectively (//info.ravenbrook.com/project/p4dti/master/manual/ug/index.html#12 section 4.2). However, this might change the status of a job, or attempt to change the status of a job the user doesn't own, and therefore violate workflow.
AnalysisWe must study the use cases in more detail and work out what it's reasonable to do, and update the documentation.
Actually, I think this is quite clear in the current documentation, "//info.ravenbrook.com/project/p4dti/master/manual/ug/index.html#17" section 4.2), so I'm closing this job. RB 2000-11-30
How foundmanual_test
Evidence<http://www.ravenbrook.com/project/p4dti/doc/2000-10-31/mahi-alpha-test/> item 16
Observed in0.3.2
Created byRichard Brooksby
Created on2000-11-22 11:51:39
Last modified byGareth Rees
Last modified on2001-12-10 19:01:56
History2000-11-22 RB Created from sources (see evidence)
2000-11-30 RB Closed (see analysis).


Change Effect Date User Description
4670 closed 2000-11-19 18:38:25 Leah Bateman Finished writing rough drafts of all but two use cases. Mildly rewrote the use cases that Richard wrote. Implemented a few style changes required by Perforce's template (mostly "&rarr;").