# The form data below was edited by super-tom_tyler
# Perforce Workshop Jobs
#
# Job: The job name. 'new' generates a sequenced job number.
#
# Status: Job status; required field. There is no enforced or
# promoted workflow for transition of jobs from one
# status to another, just a set of job status values
# for users to apply as they see fit. Possible values:
#
# open - Issue is available to be worked on.
#
# inprogress - Active development is in progress.
#
# blocked - Issue cannot be implemented for some reason.
#
# fixed - Fixed, optional status to use before closed.
#
# closed - Issue has been dealt with definitively.
#
# punted - Decision made not to address the issue,
# possibly not ever.
#
# suspended - Decision made not to address the issue
# in the immediate future, but noting that it may
# have some merit and may be revisited later.
#
# duplicate - Duplicate of another issue that.
#
# obsolete - The need behind the request has become
# overcome by events.
#
# Project: The project this job is for. Required.
#
# Severity: [A/B/C] (A is highest) Required.
#
# ReportedBy The user who created the job. Can be changed.
#
# ReportedDate: The date the job was created. Automatic.
#
# ModifiedBy: The user who last modified this job. Automatic.
#
# ModifiedDate: The date this job was last modified. Automatic.
#
# OwnedBy: The owner, responsible for doing the job. Optional.
#
# Description: Description of the job. Required.
#
# DevNotes: Developer's comments. Optional. Can be used to
# explain a status, e.g. for blocked, punted,
# obsolete or duplicate jobs. May also provide
# additional information such as the earliest release
# in which a bug is known to exist.
#
# Component: Projects may use this optional field to indicate
# which component of the project a givenjob is associated
# with.
#
# For the SDP, the list of components is defined in:
# //guest/perforce_software/sdp/tools/components.txt
#
# Type: Type of job [Bug/Feature]. Required.
#
# Release: Release in which job is intended to be fixed.
Job: P4XFER-1
Status: open
Project: perforce-software-p4transfer
Severity: C
ReportedBy: tom_tyler
ReportedDate: 2019/04/16 20:01:19
ModifiedBy: super-tom_tyler
ModifiedDate: 2019/04/16 20:01:19
Description:
Add an interactive wizard of some kind to greatly simplify
setup of a P4Transfer configuration.
It should query the user for a working directory (the root
of the workspaces and home of the transfer.cfg file), and
then query them for details of the source and target servers.
It should then ask questions that determine the set of default
flags to be used for that configuration (e.g. -k, --ignore,
etc.), and somehow persist that information, e.g. perhaps
generating a 'P4TransferWrapper.py' wrapper script that
just calls P4Transfer.py withose flags.
Then the wizard should generate the workspaces to be used
with P4Transfer on both the source and target servers. It
should login in using the credentials provided (relying on a
ticket if no password is specified, just as with normal
P4Transfer.py operation).
The workspaces should be configured with best practices for a
workspace used P4Transfer. By "best practices," it should,
for example, determine whether 'noallwrite' or 'allwrite'
option and/or the submitunchanged/leaveunchanged option is best
for a workspace to be used with P4Transfer. If there is no
best practice, just pick one.
Type: Feature