Both sides previous revisionPrevious revisionNext revision | Previous revision |
75:process_feedback_rtc [2020/05/11 09:50] – [Process Feedback RTC specific] tssr | 75:process_feedback_rtc [2024/02/15 00:00] (current) – external edit 127.0.0.1 |
---|
| |
This data can be specified in the sections **<nowiki><attributes></nowiki>** and **<nowiki><system-attribute-mappings></nowiki>** of the stages configuration file (config.xml). | This data can be specified in the sections **<nowiki><attributes></nowiki>** and **<nowiki><system-attribute-mappings></nowiki>** of the stages configuration file (config.xml). |
| |
**About the Feedback Integration** | |
| |
The RTC Feedback Integration uses the discovery mechanisms of [[https://oslc.github.io/developing-oslc-applications/eclipse_lyo/eclipse-lyo.html|OSLC]]. It is build using the OSLC library [[https://github.com/eclipse/lyo|Eclipse Lyo]]. | |
| |
===== Stages config.xml ===== | ===== Stages config.xml ===== |
| |
<!-- | <!-- |
The user will be asked to enter the following text fields. All text fields are optional. | See common feedback documentation |
- The "ident" must be unique and is used to identify the right translation property. | |
- The "type" defines, if the field is a multi-line text ("text") or a single line string ("string"). | - The "type" defines, if the field is a multi-line text ("text") or a single line string ("string"). |
- The "target" defines the id of the custom attribute in RTC (e.g. "some.custom.attribute"). | - The "target" defines the id of the custom attribute in RTC (e.g. "some.custom.attribute"). |
| |
<!-- | <!-- |
You can map Stages-Element specify information to your RTC work item. These sources are available: | See common feedback documentation |
- elementUrl e.g. https://stages.example.com/stages/index.html#/workspace/200/_vv/(process/activity/_wUV9sBbNHr-aicWx33VsQA) | |
- workspaceName e.g. "Software Engineering" | |
- workspacePath e.g. "Company | Software" | |
- creatorFullname "John Doe" | |
- creatorUsername "jdoe" | |
The "target" defines the id for the custom attribute in RTC (e.g. "some.custom.attribute"). | The "target" defines the id for the custom attribute in RTC (e.g. "some.custom.attribute"). |
Optional: The targetType defines the type of the RTC attribute. For supported RTC target types see below. | Optional: The targetType defines the type of the RTC attribute. For supported RTC target types see below. |
<attribute source="elementUrl" target="test.link" /> | <attribute source="elementUrl" target="test.link" /> |
</system-attribute-mappings> | </system-attribute-mappings> |
| |
| <!-- |
| See common feedback documentation |
| The "target" defines the id for the custom attribute in RTC (e.g. "some.custom.attribute"). |
| Optional: The targetType defines the type of the RTC attribute. For supported RTC target types see below. |
| --> |
| <custom-attribute-mappings> |
| <attribute value="Stages" target="MySourceSystemField" targetType="some.custom.attribute" /> |
| </custom-attribute-mappings> |
| |
</host> | </host> |
</feedback-system> | </feedback-system> |
</stages-config> | </stages-config> |
</code> | </code> |
| |
| ===== Technical detail ===== |
| |
| The RTC Feedback Integration uses the discovery mechanisms of [[https://oslc.github.io/developing-oslc-applications/eclipse_lyo/eclipse-lyo.html|OSLC]]. It is build using the OSLC library [[https://github.com/eclipse/lyo|Eclipse Lyo]]. |