A few questions and possible feature requests

Thanks, Sergey Merzlov . Regarding Item 1, should the “Update the value in a field” workflow action be able to accomplish this? It only seems to support setting a fixed value. Or does this have to be done via a JavaScript workflow?

Regarding Item 4, the New Ticket button appeared once I made the (already active) form Primary. Thanks!

Hi there,

For simple logic, you can use the visual workflow constructor with predefined blocks like “Update the value in a field”. For more complex scenarios, JavaScript workflows offer much more flexibility.

Glad to hear the New Ticket button appeared after setting the form as Primary!

Let me know if you have any more questions!

What I meant, Sergey Merzlov , was can the “Update the value in a field” action do something any more complicated than set a static value? If so, how do I do that? The field appears to accept only a static string value.

Also, I'm struggling to get started with JavaScript workflows. For something like this, would it be possible to get some guidance what the ‘guard’ and ‘action' should be?

For example, for a custom field “Key Code”, when it changes (i.e., is created or edited), then build another field, ‘Key Report’, which concatenates a URL prefix with the first value? Here's an example, though it doesn't appear to work, yet.

/**
* This workflow builds the Key Report field by concatenating the URL prefix with the Key Code.
*/
const entities = require('@jetbrains/youtrack-scripting-api/entities');
exports.rule = entities.Issue.onChange({
 title: 'report',
 guard: (ctx) => {
   const issue = ctx.issue;
   return issue.isChanged('Key Code');
 },
 action: (ctx) => {
   const issue = ctx.issue;
   issue.fields.KeyReport.value = 'https://lookup.example.test/report?keycode=' + issue.fields.KeyCode;
 },
 requirements: {
   KeyCode: {
     type: entities.Field.stringType,
     name: 'Key Code'
   },
   KeyReport: {
     type: entities.Field.stringType,
     name: 'Key Report'
   }
 }
});

Hi there,

The "Update the value in a field" action in the visual workflow constructor is limited to static values for string fields. However, it can offer more options depending on which field type you're updating. For your use case of dynamically building URLs in the string field, you'll need to use JavaScript workflows.

Regarding your JavaScript workflow, there's one issue with your code:

String fields don't have a value property. Change this line:

issue.fields.KeyReport.value = 'https://lookup.example.test/report?keycode=' + issue.fields.KeyCode;

To this:

issue.fields.KeyReport = 'https://lookup.example.test/report?keycode=' + issue.fields.KeyCode;

Also, make sure the workflow is properly attached to your project and doesn't have a "Requires setup" label, which would indicate configuration issues. You can find more details here: Attach Workflow to Projects

Let me know if you have any more questions!

Well I'll be, it worked. Thanks!

Should I have seen any messages in the Console area when I had this workflow open and was erroneously assigning to .value? I saw/see none, ever.

Hi,

Some errors are shown right on the issue page when applying changes that trigger a faulty rule. All custom logging (via `console.log()`) and errors are also displayed in the workflow editor console, not the browser console.

That's what I meant, the workflow editor console. I saw and see no messages on there; not that I'm explicitly calling console.log(), but I see no errors there at all.

Okay, I added an explicit console.log() call and now I see it there. I never saw errors related to trying to assign to that issue.fields.KeyReport.value property, though.

If you didn't see it, then it means the rule didn't even execute. You can try creating a test rule, add custom logging to confirm it's actually working and passes the guard, and then see if the errors appear in the console.