[BUG] 'required' does not work in HelpDesk project

Hi Viacheslav, could you let us know more about the scenario that you want to cover with your workflow in helpdesk projects particularly? We have a feature request that could be relevant in regards to online forms: JT-74721 Conditional fields for online form

Hi Stanislav,

We use a state in which the employee must choose other employees whom he involves to solve the problem. To do this, a field was created (enum multi) with the ability to select multiple users, and this function showed a dialog box for selection.

Hi,

I have a script that depends on two fields, State and Test1.

const entities = require('@jetbrains/youtrack-scripting-api/entities');
exports.rule = entities.Issue.onChange({
 title: "WF rule",
 guard: function(ctx) {
   const issue = ctx.issue;
   return issue.fields.isChanged(ctx.State) && issue.fields.becomes(ctx.State, ctx.State.WaitingForInfo);
 },
 action: function(ctx) {
   ctx.issue.fields.required(ctx.Test1, 'dfgdfg');
 },
 requirements: {
   State: {
     name: "State",
     type: entities.State.fieldType,
     WaitingForInfo: {
       name: "Waiting For Info"
     }
   },
   Test1: {
     name: "Test1",
     type: entities.User.fieldType,
     multi: true
   }
 }
});

And when you choose "Waiting For Info" State a window should appear and you should choose user.

But instead of it I get this error:

Hello,

This message is the expected result. According to our docs, this method asserts that a value is set for a custom field. If a value for the required field is not set, the specified message is displayed in the user interface. As I understand, the message is displayed. 

Feel free to describe your final goal. We will try to find a solution. 

Hello,

On the contrary, this message is exactly an unexpected result; the expected result should be a modal window.

ctx.issue.fields.required(ctx.Test1, 'dfgdfg');

Hi Viacheslav. I understand this may not be the outcome you expected, but as my colleague mentioned previously, this is the “as designed” behavior—as per the docs. We have an existing feature request that may be close or to some degree relevant to what you have in mind: JT-52446. Feel free to vote for it and/or leave a comment about the desirable implementation.

Hi,

This method works fine in all projects, but not in the HelpDesk type project. Why?

I'm not sure what you mean by the method working “fine”. The method exhibits the expected behavior, as far as we can see from the information you provided. The modal window that you are referring to may be related to the userInput property, but it is available only in action rules.

Hi,

I mean that this method works as intended. In every single project. Except HelpDesk-type projects.

Hello,

Thank you for being so patient. It looks like I figured out what you mean. The thing is that the Helpdesk uses the Lite interface. Lite doesn't show the command dialogue in this scenario at the moment for all projects (not only for Helpdesk). You can test it by switching the interface. So I created an issue for our developers to consider implementing the behaviour from the Classic UI in the Lite (and in the Helpdesk projects): https://youtrack.jetbrains.com/issue/JT-77917/The-required-method-doesnt-show-the-command-dialogue-in-the-Lite-interface

Please vote for it to stay informed of our progress. 

Hello,

thank you! 🙏🏻

You are welcome! 

Hello,

And now this function does not work in either the Classic or Lite interface...

Hello,

We updated the interface for viewing single issues in YouTrack Classic, bringing some visual enhancements that were exclusive to YouTrack Lite. As YouTrack Lite doesn't support this functionality, it has also stopped working in Classic. I agree that it is not expected, so I contacted our developers. Please follow the report I shared above for the details. Thank you. 

Hello,

the task was closed with State ‘As designed’. And it looks very strange. It was a useful feature, but it turned out that it wasn't supposed to work that way? And no one noticed before? How is this even possible?

I've added a video for comparison, you can watch it.

It literally ruined our workflows and work processes…

Is it safe to downgrade to an earlier version like 2023.2.21228?

Hello,

I'm sorry for this inconvenience. As my colleague described in https://youtrack.jetbrains.com/issue/JT-77917, the changes were applied due to the unification of the user experience reasons. Most of our customers complained about the previous behaviour. 

As for downgrading, I'm afraid it is not possible.