im importissue
imports an issue into Windchill RV&S
Synopsis
im importissue [--createdDate=value] [--createdUser=value] [--type=type] [--addSourceTrace=value] [--addSourceLink=value] [--addAttachment=value] [--addRelationships=value] [--customFieldDefinition=value] [--customFieldValue=value] [--field=value] [--richContentField=value] [--hostname=server] [--port=number] [--password=password] [--user=name] [(-?|--usage)] [(-F file|--selectionFile=file)] [-g|--gui] [(-N|--no)] [--quiet] [(-Y|--yes)] [--[no]batch] [--settingsUI=[gui|default]] [--cwd=directory] [--status=[none|gui|default]] [--forceConfirm=[yes|no]]
Description
im importissue imports an issue into the Windchill RV&S database, creating a new issue to represent it. For example:
im importissue --createdDate="12/13/2008 7:00:00 AM" --type=Defect
imports the Defect item created on 12/13/2008 at 7:00:00 AM, and creates a new item to represent it.
|
|
The Admin permission is required to use the im importissue command.
|
Options
This command takes the universal options available to all
im commands, as well as some general options. See the
options reference page for descriptions.
• --createdDate=value
specifies the date that the issue was originally created on. This option supports the following timestamp formats: MM/dd/yy h:mm:ss a z, MM/dd/yy h:mm:ss a, and MM/dd/yy hh:mm a (where a is AM or PM, and z is a timezone name, for example, for example, CEST, CET, EST, PST, or GMT+/-hours:minutes). Dates that occur in the future cannot be specified. If this option is not specified, the date and time that the command is run is recorded as the created date.
• --createdUser=value
specifies the user name of the user who originally created the issue If this option is not specified, the user running the command is recorded as the created user.
• --type=type
specifies the type of issue to create in the database.
• --addSourceTrace=value
adds a trace to a source file, where value is of the form
"field=scmSourceFieldName,server=scmServerName,port=scmPortNumber,file=fileName,project=scmProjectName[,devpath=devpathName][,projectRevision=revision] [,start=startLineNumber][,end=endLineNumber]"
|
|
• If you specify a configuration path for project=scmProjectName then devpath=devpathName and projectRevision=revision cannot be specified.
• You cannot add the same source trace more than once. In order to be considered a new source trace, the trace must have a unique combination of the following attributes: member name, server name, server port, project, project revision, development path, revision, start line number, and end line number.
|
• --addSourceLink=value
adds a link to a source file, where value is of the form
"field=scmSourceFieldName,revision=memberRevisionID, server=scmServerName,port=scmPortNumber,[file=fileName|subproject=subprojectName|isProject],project=scmProjectName[,devpath=devpathName][,projectRevision=revision] [,start=startLineNumber][,end=endLineNumber]"
|
|
• If you specify a configuration path for project=scmProjectName then devpath=devpathName and projectRevision=revision cannot be specified.
• You cannot add the same source link more than once. In order to be considered a new source link, the link must have a unique combination of the following attributes: member name, server name, server port, project, project revision, development path, revision, start line number, and end line number.
|
• --addAttachment=value
adds attachments, where value is of the form
"field=fieldName,path=pathToFile[,name=nameOfAttachment][,summary=shortDescription]".
|
|
Attachment size limits are set by your administrator. The default attachment size limit is 4 MB.
|
• --addRelationships=value
specifies the related issues for the issue, where value is of the form [fieldname]:id[linkflags][,...].
• --field=value
specifies a value for the field, of the form fieldName=fieldValue.
|
|
It is possible to set the state value to any state in the workflow, including an the end state if there is one.
|
• --richContentField=value
specifies a rich content field and its value, where value is of the form "richcontentfieldname=fieldValue".
To specify a link to an item by ID:
<a href="mks:///item?itemid=ID">DisplayText</a>
For example: <a href="mks:///item?itemid=4547">Part Requirement</a>
To specify a link to an item by ID and label:
<a href="mks:///item?itemid=ID&label=LABEL">DisplayText</a>
For example: <a href="mks:///item?itemid=4547&label=EDF-343">Part Requirement, Label EDF-343</a>
To specify a link to an item by ID and revision:
<a href="mks:///item?itemid=ID&revision=REVISION">DisplayText</a>
For example: <a href="mks:///item?itemid=4547&revision=1.2">Part Requirement, Revision 1.2</a>
To specify a link to an item by ID and date:
<a href="mks:///item?itemid=ID&asof=DATETIME">DisplayText</a>
,where date is in the format for your locale; such as US date formats "mm/dd/yy", "mm/dd/yyyy", or "mmm d, yyyy" with the time "h:mm:ss a".
For example: <a href="mks:///item?itemid=4547&asof=03/25/2012 12:04:00 AM">Part Requirement, March 25, 2012 12:04am</a>
|
|
In the korn shell command line interface, HTML tags must be surrounded by quotes, for example,"<b>Feature Overview</b>". In the Windows command line interface (cmd.exe), the ^ escape character must precede the < and > characters in HTML tags, for example, ^<b^>Feature Overview^</b^> . You may need to escape nested " characters, for example, --richContentField=Description="<a href=\"mks:///item?itemid=4547\">Part Requirement</a>".
|
See Also
