Uploaded image for project: 'Camunda Optimize'
  1. Camunda Optimize
  2. OPT-2817

Make clear where to find the migration instructions in the docs

    • Icon: Task Task
    • Resolution: Done
    • Icon: L3 - Default L3 - Default
    • 2.7.0
    • None
    • documentation
    • None

      AT:

      • the parent title is rename from Migration & Upgrade to Migration & Upgrade Instructions
      • there is a warning note in each migration notes on where to find the actual migration instructions to emphasize where to find them
      • the subtitle Migrate instruction from 2.1 onwards of the Migration & Upgrade is renamed to Migrations Instructions
      • the changes are backported to all the existing documentation branches up to 2.4
      • the changes have been released so that they are available to our users

      Context:
      Users had troubles to find the right page or the upgrade instructions in general.

        This is the controller panel for Smart Panels app

            [OPT-2817] Make clear where to find the migration instructions in the docs

            Johannes added a comment -

            sebastian.bathke: a couple of hints:

            I only backport the changes to 2.4. because:

            • the docs directory structure changes with 2.4 and it would be quite some effort to backport the changes to the old structure as well
            • the were only two known customers that used 2.3 and even they already upgraded to later versions. Thus, no need to backport the changes to older docs versions as well.

            The changes were directly merged since I didn't want to create 5 PR's.

            Johannes added a comment - sebastian.bathke : a couple of hints: I only backport the changes to 2.4 . because: the docs directory structure changes with 2.4 and it would be quite some effort to backport the changes to the old structure as well the were only two known customers that used 2.3 and even they already upgraded to later versions. Thus, no need to backport the changes to older docs versions as well. The changes were directly merged since I didn't want to create 5 PR's.

              Unassigned Unassigned
              johannes.heinemann Johannes
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: