Workflow to update a custom field when either of two other custom fields are updated.

Hello,

Thank you for contacting YouTrack community forums. Please find some hints below:

1. Your workflow needs to fire on updating either Salesforce Contacts or Forum Contacts field. You can find a corresponding example of how to fire on the field update here: https://www.jetbrains.com/help/youtrack/devportal/Workflow-Assignee-Visibility-Group.html#warn-assignee. The rule logic should take both fields' values and put the sum in the Grand Total field. To assign a new value to the field, please use ctx.issue.fields.<fieldname> = <new value>. You can find an example of assigning new values to the fields here: https://www.jetbrains.com/help/youtrack/devportal/Workflow-Pomodoro-Timer.html#pomodoro-states

2. Do you want to force the users somehow to add 1 to these fields? Or do you just want to recalculate the sum? If the latter, the logic is the same as in p.1. The workflow should fire on changing the Salesforce Contacts or Forum Contacts fields and recalculate the Grand Total field. 

For example, the following sample of code will fire on changing issue type to Epic, calculate the sum of the Importancy and the Story points fields and put it into the Importancy field.

var entities = require('@jetbrains/youtrack-scripting-api/entities');
var workflow = require('@jetbrains/youtrack-scripting-api/workflow');

exports.rule = entities.Issue.onChange({
  title: 'check deleted',
  guard: function(ctx) {
    return ctx.issue.fields.becomes(ctx.Type, ctx.Type.Epic);
  },
  action: function(ctx) {
    var issue = ctx.issue;
    ctx.issue.fields.Importancy += ctx.issue.fields['Story points']; 
  },
  requirements: {
    Type: {
      type: entities.EnumField.fieldType,
      Epic: {
        name: 'Epic'
      },
      Bug: {
        name: 'Bug'
      },
      Task: {
        name: 'Task'
      }
    }
  }
});

Please let me know if it helps. 

I have gotten the following to work, there is just one minor problem in the following use case.
If an updater makes a mistake of updating the wrong field, for example, updated the Salesforce Contacts instead of Forum Contacts, and changes it back to zero, the Grand Total Value does not change. For any other value but zero, the Grand Total computes normally. 

Example, 

If I update the custom field SF Contacts to 1 and leave the Forum Contacts at 0, the Total Contacts  updates correctly to 1.

If I revert the custom field SF Contacts to 0, and leave the Forum Contacts at 0, The Total Contacts stays at 1. 

var entities = require('@jetbrains/youtrack-scripting-api/entities');

exports.rule = entities.Issue.onChange({
   title: 'Compute Grand Total',
  guard: (ctx) => {
    return ctx.issue.fields.isChanged(ctx.SFContacts) && ctx.issue.fields.SFContacts || ctx.issue.fields.isChanged(ctx.ELHContacts) && ctx.issue.fields.ELHContacts;
  },
  action: (ctx) => {
    var issue = ctx.issue;
    var sfNum = ctx.issue.fields.SFContacts;
    var elhNum = ctx.issue.fields.ELHContacts;
    var grandNum = sfNum + elhNum;
    ctx.issue.fields.TotalContacts = grandNum;
  },
  requirements: {
    SFContacts: {
        type: entities.Field.integerType,},
    ELHContacts: {
          type: entities.Field.integerType,},
    TotalContacts: {
          type: entities.Field.integerType,},
  }
});

Hi,

I believe the root cause is that the workflow checks if the ctx.issue.fields.SFContacts and ctx.issue.fields.ELHContacts fields are set. In this case, the rule doesn't trigger when the field is reset (set to 0). Could you please try to modify your guard condition to the following and let me know if it helps?

return ctx.issue.fields.isChanged(ctx.SFContacts) || ctx.issue.fields.isChanged(ctx.ELHContacts);

What syntax do I write (e.g. after ctx.) for field labels that include a whitespace?

Hi Julian Dumitrascu . The alias shouldn't contain any whitespaces, but the field requirement can have a name with whitespaces:

action: (ctx) => {
    ctx.issue.fields.IntegerField = 10;
  },
  requirements: {
    IntegerField: {
        type: entities.Field.integerType,
        name: 'Integer Field'
        },
});

For more information, see Requirements.