You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This comment was imported from JIRA and written by user @yanavasileva
@rob2universe, thank you for raising this ticket.
Please note that I removed the Modeler from the description/title of the ticket as the CAM project is only for Camunda Platform product. The request for the Modeler could be raised as depended on this ticket (as the implementation from our side will be used in the tool) in the Modeler issues: https://github.com/camunda/camunda-modeler/issues
I will send the ticket for a decision, however, please let us know if you are willing to raise a PR for this.
thanks for creating this request. I think it generally makes sense to add such an option to the deployment dialog in Cockpit (and the parameter in the REST API).
In order to determine a priority for this, can you please tell us if there is a specific use case or customer you need this for already?
thanks again for bringing this to our attention. We think this would be a valid addition to the web apps in general and the deployment API in particular. However, due to other commitments and priorities we will not add this to our roadmap for now.
As Yana already offered, we are happy to accept and help with PRs if you want to move forward with this.
we have added this ticket to our backlog. It will be part of the next prioritization rounds, which does however not yet mean that we will work on this in the near future.
If you want to go ahead and build this yourself by providing a PR, let us know.
This issue was imported from JIRA:
User Story (Required on creation):
Deployments can be scheduled when deploying a process model via Cockpit
Functional Requirements (Required before implementation):
Technical Requirements (Required before implementation):
Limitations of Scope (Optional):
Hints (Optional):
Links:
The text was updated successfully, but these errors were encountered: