P4DTI issue job000007

TitleThe fixes keyword can't be set on submit (except to "closed")
Assigned userRichard Brooksby
DescriptionEach Perforce interface needs a way to set the "fixes keyword" to something other than "closed" when submitting or creating a new change.
Currently, when submitting, each interface brings up a pick list of jobs. If any jobs are chosen from the list, then a fix is created that links the submitted changelist to the job, and that fix has keyword "closed" (see p4 fixes -s) and the job's status is therefore changed to "closed".
Each interface needs to provide a way to set this keyword (and therefore the job status) to something other than "closed" -- in fact, any legal value for the "status" field in a job.
AnalysisAnalysis of this problem is up to Perforce. See the e-mail referenced above for my ideas. RB 2000-09-19
Chris has implemented a mechanism for this in the command line interface.
I think the designer of each interface will have their own ideas about how best to present this, but FWIW I suggest that each job is listed with a check box to say whether to fix the job at all, and some sort of selection control from which the user can choose the keyword. A drop-down menu would be ideal, I think. Second best would be just a selection control which included the magic "notfixed" value which tells the server not to fix the job. Third best would be a textual interface similar to the one that Chris has implemented for the command line. RB 2000-11-27
Perforce have supplied a server change which gives an interface in the Windows GUI and the development environment plug-ins (though the latter don't have a drop-down menu). See <http://info.ravenbrook.com/mail/2000/12/06/12-51-36/0.txt>. RB 2000-12-06
How foundmanual_test
Test procedure<http://www.ravenbrook.com/project/p4dti/master/test/test_p4dti.py>, section 10.4.
Created byRichard Brooksby
Created on2000-09-19 23:40:19
Last modified byGareth Rees
Last modified on2001-12-10 18:54:10
History2000-09-19 RB Added from e-mail "A submit form interface to fixes keywords" <http://info.ravenbrook.com/mail/2000/09/19/00-18-11/0.txt>.
2000-11-27 RB Added clarification that this is needed in all interfaces to Perforce that support fixing, and some suggestions for how to do it.
2000-12-06 RB Added reference to mail about Perforce's fix and closed with changes to the manual in version 0.4.


Change Effect Date User Description
5534 closed 2000-12-06 13:11:32 Richard Brooksby Updating the UG to include instructions for setting the fixes keyword in the development environment plug-ins.
5519 open 2000-12-06 10:54:38 Gareth Rees Added Perforce server P4D/NTX86/2000.2beta/18974 to imported materials.