Stages Documentation

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Last revisionBoth sides next revision
75:process_feedback_redmine [2020/04/14 13:08] – [Supported Redmine Custom Fields] tssr75:process_feedback_redmine [2020/07/13 11:12] – fnpk
Line 33: Line 33:
  
       <!--       <!--
-      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 "target" defines the name of the field in Redmine (e.g. "assigned_to_id").       - The "target" defines the name of the field in Redmine (e.g. "assigned_to_id").
       - The targetType defines whether the value is a custom attribute or built-in and defines the type of the value.       - The targetType defines whether the value is a custom attribute or built-in and defines the type of the value.
Line 46: Line 45:
  
       <!--       <!--
-      You can map element specify information to your Redmine 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 custom field id for the field in Redmine (e.g. "1").       The "target" defines the custom field id for the field in Redmine (e.g. "1").
       (To get the custom field ids go to http://redmine.excample.com/issues/[issueId].json)       (To get the custom field ids go to http://redmine.excample.com/issues/[issueId].json)
Line 63: Line 57:
         <attribute source="creatorUsername" target="assigned_to_id" targetType="user"/>         <attribute source="creatorUsername" target="assigned_to_id" targetType="user"/>
       </system-attribute-mappings>       </system-attribute-mappings>
 +      
 +      <!--
 +      See common feedback documentation
 +      The "target" defines the custom field id for the field in Redmine (e.g. "1").
 +      (To get the custom field ids go to http://redmine.excample.com/issues/[issueId].json)
 +      Optional: The targetType defines the type of the Redmine field. Supported fields see below.
 +      -->
 +      <custom-attribute-mappings>
 +        <attribute value="Stages" target="MySourceSystemField" />
 +      </custom-attribute-mappings>
     </host>     </host>
   </feedback-system>   </feedback-system>
Line 93: Line 97:
   * User: <nowiki>targetType="custom.user''</nowiki>   * User: <nowiki>targetType="custom.user''</nowiki>
  
-To identify the IDs of the custom fields of your issues, log in to redmine. Make sure, there is at least one existing issue in the project. Navigate to this URL: <no-wiki>https://<redmine-server-name>/issues/1.json </no-wiki>.+To identify the IDs of the custom fields of your issues, log in to redmine. Make sure, there is at least one existing issue in the project. Navigate to this URL: <nowiki>https://<redmine-server-name>/issues/1.json </nowiki>.
  
 You will get the structure of the issue in JSON format as follows: You will get the structure of the issue in JSON format as follows:
  
 {{ :feedback:redmine:custom-fields.png?200 |}} {{ :feedback:redmine:custom-fields.png?200 |}}
 +
 +==== Be aware ====
 +
 +  * If you choose target type **user**, then the users must be valid Redmine users. Otherwise the ticket creation will fail.