im checksourcetraces
displays invalid source traces for issues
Synopsis
im checksourcetraces [--fields=field,field,...] [--fieldsDelim=value] [--query=[user:]query] [--queryDefinition=query] [(-?|--usage)] [(-F value|--selectionFile=value)] [(-N|--no)] [(-Y|--yes)] [--[no]batch] [--cwd=value] [--forceConfirm=[yes|no]] [--hostname=value] [--port=value] [--password=value] [--user=value] [--settingsUI=[gui|default]] [--status=[none|gui|default]] item id...
Description
im checksourcetraces lists issues with traces to source files that have an invalid project configuration path or that do not trace to the current member revision.
Options
This command takes the universal options available to
im commands, as well as some general options. See the
options reference page for descriptions.
• --fields=field,field...
specifies the issue field(s) to check for source traces. Only source trace field types can be specified.
• --fieldsDelim=value
specifies the string to be used as a delimiter between the fields in the display.
• --query=[user:]query
specifies the query used to populate the issue selection. Includes the name of the user who the query belongs to and the query name, for example, mchang:ActiveDefects. You do not have to specify the user name, but you must specify the query name. This option is useful when multiple users have the same name for a query.
|
|
Integrity Lifecycle Manager initially assumes that text before the first colon (:) is a user name and text after it is a query name. If Integrity Lifecycle Manager fails to find a matching user name and query name, it searches for a query name matching the exact text. For example, if you type mchang:FunctionalSafetyRequirements, Integrity Lifecycle Manager searches for the Functional Safety Requirements query created by mchang. If Integrity Lifecycle Manager cannot find the query and/or user, it searches for the mchang:FunctionalSafetyRequirements query created by any user.
|
• --queryDefinition=query
specifies a string to define the query constraints for the query used to populate the issue selection. The <querydefinition> must be of the same format as the query definition for a query. For details of the query definition format, see the reference page for the --im createquery command.
• issue id
specifies the issue identification number of the issue you want to check source traces for. Overrides the --query option.
See Also
