Describe the bug
Using a workflow definition in XML format with display tags "schedule" or "upload" always leads to the workflow being shown in both parts of the admin UI, even when only one of the tags is used.
To Reproduce
- Create "WF upload" with the following tags definition:
...
<tags>
<tag>upload</tag>
</tags>
...
- Create "WF schedule" with the following tags definition:
...
<tags>
<tag>schedule</tag>
</tags>
...
- Create a new event in the admin UI and select "Upload" as source. The "Select workflow" dropdown shows both "WF upload" and "WF schedule".
- Create another new event in the admin UI and select "Schedule XXX events" as source. The "Select workflow" dropdown once again shows both "WF upload" and "WF schedule".
Expected behavior
When selecting "Upload" as source for the new event, the "Select Workflow" dropdown should only contain "WF upload". Respectively, when selecting "Schedule XXX event(s)" as source for the new event, the "Select workflow" dropdown should only contain "WF schedule".
User environment:
- Device: PC
- OS: Debian 12
- Browser: Chrome
- Version: 116.0.5845.96
Additional context
The newer YAML format is not affected by this.
In addition, if both tags are absent, the workflow is correctly hidden from both parts of the admin UI.
Describe the bug
Using a workflow definition in XML format with display tags "schedule" or "upload" always leads to the workflow being shown in both parts of the admin UI, even when only one of the tags is used.
To Reproduce
Expected behavior
When selecting "Upload" as source for the new event, the "Select Workflow" dropdown should only contain "WF upload". Respectively, when selecting "Schedule XXX event(s)" as source for the new event, the "Select workflow" dropdown should only contain "WF schedule".
User environment:
Additional context
The newer YAML format is not affected by this.
In addition, if both tags are absent, the workflow is correctly hidden from both parts of the admin UI.