time schedule "every day" runs wrong Follow

Hello Andy,

Each on-schedule rule has a filter, which stores a search query that determines which issues are considered for processing by the rule. So in case of an on-schedule rule that creates issues, you need to specify an anchor issue there. Otherwise, the rule will be executed for all issues. Please refer to the example in this documentation section.

Hello Alisa,

thanks for your quick answer and your links. You´re right, i didn´t write anything in the field "filter". I tried to select an issue from my project board, but the search don´t suggest any issues. It seems the search function don´t works there.

I tried another workflow with action "create issue" (all parameters like before and field "filter" was empty too). But with this action no issue was created. Then i tried to fill the field "filter" manually like "ticket id: SB-483" or "ticket id: #SB-483" or "SB-483" or "#SB-483". But even no issue was created. How i have to fill the "filter" field?

I hoped with this workflow builder that you can easily create workflows. But even such a simple workflow without conditions and only one action doesn´t work. It´s really frustrating.

best regards,

andy

You need to use the "#SB-483" syntax. Is this SB-483 issue being from the same project that uses the workflow? Please make sure that the issue is in the same project. For example, this workflow works properly and creates only one issue:

Please note that the project is DEMO, and the anchor issue is DEMO-70.

I tried it like this now but unfortunately something goes wrong again.

This is my workflow:

And this is the issue in the same project board:

I filled the filter field with "#SB-483" (but there is no link behind, just a text) but it doesnt work.

In this moment i found that there is a event log. This is the message:

What can i try to fix this?

I tried another way without filling "filter" field. In the event log there is the same message for every issue in our project board:

Ok, now i got it. The field "Type" is the problem... If this is defined in the workflow, it goes wrong and no issue will be created. The other fields, like priority, aren´t a problem. If only priority is choosen, the issue was created.

I don´t understand why, but thats ok. It´s fine for me when i don´t use the field.

Thank you Alisa :)

Andy,

I suppose that your workflow was affected by this bug. It is already fixed, and the fix will be released in the next YouTrack version, so stay tuned. Please excuse us for the inconvenience caused.