Uploaded image for project: 'camunda BPM'
  1. camunda BPM
  2. CAM-12622

Enable Team Collaboration with Camunda Modeler

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Won't Fix
    • Icon: L2 - Critical L2 - Critical
    • None
    • None
    • camunda modeler
    • None

      Background:

      A Camunda model is saved in xml. Even small changes in xml may cause non-mergable conflicts. The merge conflicts efficiently hinder people working on the same model at the same time. To This reduces efficiency a lot. It influences our model design heavily. Because efficiency is a non-negotiable requirement, we design many small models instead of large ones. Business-wise, this is a great loss, since we can't read our business processes like they really are any more, just small pieces of them at the same time.  I am in my third team now, where we have the same problem with the models. 

      Request: 

      Make Camunca models mergeable, or provide a merge tool, or whatever. It should be no problem to work 3-4 developers at one model at the same time. Merging should be easy. This is an old problem, practically all teams have the problem and it causes huge problems. It can be one of your best selling points if you fix it. 

        This is the controller panel for Smart Panels app

            [CAM-12622] Enable Team Collaboration with Camunda Modeler

            Michal Dytko added a comment -

            Hi olsen,

            Thanks for contacting us with this issue.

            A short question: was this issue meant to be raised in our support project?

            The difference between the Support project and the Camunda BPM project is that when raising issues in the Camunda BPM project, they are not subject to the agreed SLAs and they can be viewed by all users. In contrast, issues raised in the Support project can only be seen by your authorized support contacts and us. You can find more information in our documentation.

            If you intended to raise a support issue, please let us know and we'll move this issue to the support project.

            Best regards,
            Michal

            Michal Dytko added a comment - Hi olsen , Thanks for contacting us with this issue. A short question: was this issue meant to be raised in our support project? The difference between the Support project and the Camunda BPM project is that when raising issues in the Camunda BPM project, they are not subject to the agreed SLAs and they can be viewed by all users. In contrast, issues raised in the Support project can only be seen by your authorized support contacts and us. You can find more information in our documentation . If you intended to raise a support issue, please let us know and we'll move this issue to the support project. Best regards, Michal

            badr added a comment -

            Hi @Dytko, Michael,
            thanks for asking. I already raised an issue within a support Project some 6-12 months ago. We are still not really able to merge, so I this time I wanted the issue publicly visible to everyone. 

            Best regards,

            Badr

            badr added a comment - Hi @Dytko, Michael, thanks for asking. I already raised an issue within a support Project some 6-12 months ago. We are still not really able to merge, so I this time I wanted the issue publicly visible to everyone.  Best regards, Badr

            Thorben Lindhauer added a comment -

            We are closing this ticket as part of our backlog grooming. Reasons:

            • This is a question for product support or the user forum
            • It is for a project not in the scope of the CAM tracker

            Thorben Lindhauer added a comment - We are closing this ticket as part of our backlog grooming. Reasons: This is a question for product support or the user forum It is for a project not in the scope of the CAM tracker

              Unassigned Unassigned
              olsen badr
              Votes:
              2 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: