• Your administrator can configure long text fields to support rich content. Rich content enhances the display of text in long text fields by adding formatted text, tables, background colors, images, and hyperlinks. From the CLI, rich content is applied using a limited set of HTML elements and attributes. For a complete list of supported elements and attributes, see the Centre d'aide Windchill RV&S.

• Your administrator defines which issue types and custom fields you are allowed to edit. If your administrator defines a field as a logging text field, you may only enter new text and not edit existing text.

• Displayed date fields do not change based on the time zone that a user is operating in; however, displayed date/time fields vary based on the time zone that a user is operating in.

• You cannot edit historical versions of issues.

• Relevance and editability rules are evaluated on the Windchill RV&S Client’s time zone.

• Computed expressions return dates/times in the Windchill RV&S Client’s time zone and perform calculations in the Windchill RV&S Server’s time zone where appropriate.

• The list of users in the Assigned User field is limited to those with permissions to the issue’s project. The same applies to the Assigned Group field.

• Depending on your workflow, you may not be able to edit an issue that is in an end state.

• Your administrator may include the time in date fields. You can specify the time when you select a date from the calendar. Time is specified from 00:00:00 to 23:59:59 inclusive in 24 hour format; however, Windchill RV&S displays the time in 12 hour format. For example, specifying 13:56:45 displays the time as 1:56:45 PM. If you do not specify a time, the current time displays in the date field.

• To retrieve metrics from a configuration management project related to the issue you are editing, your administrator may define a field that accepts a configuration management project as a value. Optionally, you can specify a checkpoint revision or development path. If you specify a configuration management project and a checkpoint, then save the issue, one or both of the following may occur when you view the issue in the GUI or Web interface:

• One or more computed expressions in the issue calculate specific metrics about the project, displaying the results as a read-only value in a computed field (the visibility of the computed field depends on the field’s relevance rules). For example, once you specify a project for the Source Code field, a Lines of Code field could calculate and display the number of lines of code in that project. As lines of code are added or removed from the project, the Lines of Code field updates to display the new value.

• A metrics hyperlink displays in the configuration management project field. Clicking the hyperlink displays various configuration management metrics about the project.

• You cannot set a date field to null if the date has been previously set.

• Your administrator may include the time in date fields. You can specify the time when you select a date from the calendar. Time is specified from 00:00:00 to 23:59:59 inclusive in 24 hour format; however, Windchill RV&S displays the time in 12 hour format. For example, specifying 13:56:45 displays the time as 1:56:45 PM. If you do not specify a time, the current time displays in the date field.

• You can modify a value from a mandatory field and save it.

• If your administrator has set up electronic signatures, you may need to provide your user name and password when making specific edits to an issue. For example, you could be required to provide an electronic signature when you change an issue’s state to Completed.

• Integer fields allow a maximum of nine digits and floating point fields allow a maximum of 15 digits. Your administrator can define default, minimum, and maximum values.

• By default, Windchill RV&S allows file attachments to a maximum size of 4 MB and a maximum of 255 characters for file names. Your administrator may define a higher or lower limit depending on the requirements of your system. You can also attach more than one file to a single issue.

• If you attempt to save changes to an issue after another user saves changes to the same issue, the following error message may appear: Could not save modified issue: The issue was changed by another user after you began your edit. Typing Cancel discards your changes. Typing OK displays your unsaved changes to the issue. PTC recommends copying your changes, canceling the issue, then re-editing the issue and adding your changes.

• Setting a user, group or project field to an inactive value results in an error message.

• Inactive pick list values cannot be specified for pick list fields; however, pick list fields retain inactive pick list values. If you edit a multi-valued pick list field, inactive pick list values can no longer be specified, even if only one of the values was previously inactive.

• If an issue contains multi-valued user or group fields with inactive values, editing the inactive values and saving the issue prompts you to leave the fields unchanged or clear the inactive values.

◦ VersionedTestSuiteID is the ID of the versioned test suite item that the specified versioned test case belongs to.

◦ VersionedTestCaseID is the ID of the specified versioned test case.

◦ If there are no differences in the updated attachment, the existing attachment is not updated.

◦ If the specified attachment does not exist, it is added to the item.

◦ If the updated attachment exists, but there are differences, the existing attachment is removed and the new attachment is added.

◦ The comparison of attachments is based on a message dialog algorithm (MD5) which relies on a checksum to calculate and compare the size of the attachment files. This comparison method is not guaranteed to work in all cases and it is possible to have collisions between two different attachments that are identical in size. While such collisions are rare, to avoid any possibility of collisions when using the im editissue command, you can manually update the attachments using the --addAttachment and --removeAttachment command options.

◦ If you are specifying a variant or build project for project=scmProjectName use a keyword string. For build projects, make sure you specify the build keyword (#b=) immediately after the top level project keyword (#). For more information on keyword strings, see the description for --project=project under general options on the options reference page.

◦ 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.

◦ 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.

◦ VersionedTestSuiteID is the ID of the versioned test suite item that the specified versioned test case belongs to.

◦ VersionedTestCaseID is the ID of the specified versioned test case.

◦ You can specify the configuration path for project=scmProjectName using a keyword string. For more information on specifying project paths using a keyword string, see the description for --project=project under general options on the options reference page.

◦ If you specify a configuration path for project=scmProjectName then devpath=devpathName and projectRevision=revision cannot be specified.

◦ You can specify the configuration path for project=scmProjectName using a keyword string. For more information on specifying project paths using a keyword string, see the description for --project=project under general options on the options reference page.

◦ If you specify a configuration path for project=scmProjectName then devpath=devpathName and projectRevision=revision cannot be specified.

• Commands: im copyissue, im createissue, im extractattachments, im viewissue

• Miscellaneous: options