Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Higher-level processes should not have a workflow #3307

Closed
matthias-ronge opened this issue Mar 18, 2020 · 1 comment · Fixed by #3753
Closed

Higher-level processes should not have a workflow #3307

matthias-ronge opened this issue Mar 18, 2020 · 1 comment · Fixed by #3753
Assignees

Comments

@matthias-ronge
Copy link
Collaborator

Currently, higher-level processes get the same workflow as their children, and tasks, and the tasks are open for operator processing, as is usual at the beginning of workflow.

Goal: There is nothing to do with higher-level processes. They should be hidden (like completed processes) and have no tasks, especially no open tasks. Solution is subject to discussion, no production template seems the most logical. But can also be a dummy workflow without steps, or whatever.

@matthias-ronge
Copy link
Collaborator Author

Twinned with issue #3190

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants