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
75:process_feedback_redmine [2020/04/14 11:52] – [Process Feedback Redmine specific] tssr75:process_feedback_redmine [2024/02/15 00:00] (current) – external edit 127.0.0.1
Line 3: Line 3:
 First of all, create or choose a Redmine project where the feedback will be collected. First of all, create or choose a Redmine project where the feedback will be collected.
 You need to get the identifier for that project: You need to get the identifier for that project:
-{{:feedback:redmine:project-identifier.png?300|}}+ 
 +{{ :feedback:redmine:project-identifier.png?300 |}}
  
 Second, you need a user for creating the issues in that project. Navigate to the account details page and get the API access key from there. Second, you need a user for creating the issues in that project. Navigate to the account details page and get the API access key from there.
  
-{{:feedback:redmine:access-key.png?300|}}+{{ :feedback:redmine:access-key.png?300 |}}
  
 Stages will use the [[https://www.redmine.org/projects/redmine/wiki/Rest_api|Redmine REST API]] interface to create the items. Stages will use the [[https://www.redmine.org/projects/redmine/wiki/Rest_api|Redmine REST API]] interface to create the items.
Line 32: 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 45: 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 62: 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 68: Line 73:
  
 ==== Supported Redmine Issue Fields ===== ==== Supported Redmine Issue Fields =====
-  * subject: <nowiki>targetType=""</nowiki>+Example: 
 + 
 +<code xml><attribute ident="attributeIdent" type="text" target="description" /></code> 
 + 
 +  * subject: <nowiki>targetType=""</nowiki> (Subject is always enabled and must not be configured in config.xml)
   * description: <nowiki>targetType=""</nowiki>   * description: <nowiki>targetType=""</nowiki>
   * assigned_to_id: <nowiki>targetType="user"</nowiki>   * assigned_to_id: <nowiki>targetType="user"</nowiki>
Line 87: Line 96:
   * Link: <nowiki>targetType="custom''</nowiki>   * Link: <nowiki>targetType="custom''</nowiki>
   * 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: <nowiki>https://<redmine-server-name>/issues/1.json </nowiki>.
 +
 +You will get the structure of the issue in JSON format as follows:
 +
 +{{ :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.