From OSLC perspective, the Shape of a resource is the set of properties that composes it. Changing the issue shape implies, therefore, to change the set of properties/fields that are exposed or visible to other resources/applications. In the Rebuilding TRS Feeds topic, the complete default list of all Issue system fields that are exposed to other OSLC applications can be consulted . Now, since these exposed properties are the ones used by reporting tools (like IBM Report Builder) to build their reports, it can very convenient to modify the Jira Issues' Shapes with Jira custom fields.
By setting this configuration, you will be able to include or remove Jira custom fields from the exposed properties.
Be aware that since Jira custom fields can have very different implementations on their own, it is not guaranteed
that all of them will work as expected. This means that they might end up with an meaningless value when displayed. For this, the configuration page
Status column to inform the supporting level:
Before passing to the configuration steps, it is worth to mention that this configuration will apply for all issues of all projects sharing an Issue Type Scheme. Since these changes need to reported to all TRS feeds clients, it is highly recommended to use it very carefully as it may trigger a lot of TRS notifications and HTTP requests .
JIRA ADMINISTRATION > Manage appspage.
Issue Shapesoption in the
Statusof the configured custom fields. In the bottom of the table, you will find the same control used to configure the fields of a screen , use it in the same way to select and add a custom field in the Issue shape.
To remove a custom field: