To configure a trigger, please follow the steps:

  1. Go to the Triggers page and click Create Trigger.
  2. In the If field, enter the desired HP ALM filter to decide which issues will get automatically synced to the other side. 

    The formatting used should be allowed by the HP ALM REST API  (See Filtering a Collection of Entities):

    Filtering a Collection of Entities
    Filtering a Collection of Entities
    A GET statement that returns a large amount of data can stress the database server and cause performance degradation for all users. To minimize the impact:
    filter the entities to be returned.
    
    ...
    
    Query Syntax
    
    The elements of a query are:Comparison operators:<,>,<>,>=,<=
    Logical operators: and, or, not
    Literals: String that represent the value of an expression. If a value contains spaces, it must be contained within single or double quotes. Literals can contain the '*' wild card.
    Pairs of parenthesis
    
    ...
    The expression applied to a field is contained in square brackets "[]".
    The field delimiter is a semicolon ";" .
    The only operation supported between fields is AND. The AND operation is implicit and is not specified in the query syntax. Only the ";" delimiter is specified.
    For example:
    id[>1 AND NOT 5]; status[Ready or Design]
    
    This query specifies any test whose ID is above one, excluding test 5, and whose status is Ready or Design.
    
    
    Examples of valid queries
    
    
    Field Names
    Fields are identified by logical name. To get the list of fields for an entity, use the XML returned by a GET on the customization fields Collection.
    This is an example of a Field element:
    <Field PhysicalName="TS_ATTACHMENT" Name="attachment" Label="Attachment"">
    
    The PhysicalName attribute of the Field is the column name in the project database. The Label is the display string that can be customized.
    The Name attribute is the logical name. Use the logical name value to specify fields in:
    group specifications
    order specifications
    Input XMLs to create or update an entity
    
    Cross Filters
    If there is a relational connection between two entity types, a collection can be filtered on the related entities. Use the unique alias that represents the relation for the cross filter. For an example of how to know if an alias is unique, see the example in the Relations topic.
    The expression for the related entity is <alias>.<logical field name><filter expression>.
    For example, because tests can be linked to defects, the tests collection can be filtered by defect fields:
    ...connected-to-defect.name["Widget wobbles*"]
    See Relations, the relations resource and the Relation XSD.
    
    Examples
    Single entity expressions
    status[NOT (Ready or Design)]
    status[(NOT Ready or Design]
    status[Ready or NOT Design]
    id[>=1 And NOT = 5]
    exec-status['Not Completed']
    exec-status['Not Com*']
    
    Cross filter expressions with entity names
    Tests in status "Ready" that are linked to defects assigned to user SallyQA:
    status[Ready]; defect.owner[SallyQA]
    Tests that are linked to defects assigned to user joe:
    defect.owner[joe]
    
    Cross filter expressions with relation aliases
    Design steps that call tests named D*:
    used-by-test.name[D*]
    Design steps that are part of tests named S*:
    has-parts-test.name[S*]
    
    Exclusive Filter
    To return the resources that do not meet the conditions applied to an entity, add {entity}.inclusive-filter[false] to the filter. The effect is to exclude the resources that would be returned if inclusive-filter[false] were not specified and to return the rest. For example:
        defect.id[1];defect.status[Closed or Fixed];requirement.id[1];defect.inclusive-filter[false]
    This query returns tests that are linked to the requirement whose ID is 1, excluding tests linked to the defect whose ID is 1 and excluding tests linked to defects that are fixed or closed. Note that since inclusive-filter[false] is applied to the defect entity, only the clauses for defect are treated as exclusion clauses. The requirement clause is applied as an inclusion clause.

    Taken from HP ALM docs > How to Do Common Tasks > Query a Collection of Entities > Filtering a Collection of Entities

    Following query triggers the sync on defects which have status 'Open'
    status[Open]

         

3. Select the relation you want to sync with under Then sync with connection field.

4. Optionally, input information to keep a reference for the trigger in the Notes field.

6. Active? Toggle to activate the trigger after creation. In case the toggle is disabled, the trigger won't work.