Uploaded image for project: 'Migration Platform'
  1. Migration Platform
  2. MIG-186

Give users the option to remove the migrated text from fields

XMLWordPrintable

    • 754

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Problem Definition

      Currently, when using JCMA all fields(and other entities) migrated by the add-on have a description added with the date they were migrated:

      Suggested Solution

      Grant users the option to choose whether they want to have this description added or not.

      Workaround

      A workaround is available on JCMA v1.7.8 and later:

      • Navigate to <jira_Server>/secure/SiteDarkFeatures!default.jspa
      • Apply the dark feature: com.atlassian.jira.migration.skip.migrated.on.text

        1. Screen Shot 2020-05-15 at 14.16.46.png
          Screen Shot 2020-05-15 at 14.16.46.png
          7 kB

            [MIG-186] Give users the option to remove the migrated text from fields

            Mohan Rao added a comment -

            ok..

             

            Mohan Rao added a comment - ok..  

            Rananjay Pathania added a comment -

            https://getsupport.atlassian.com/browse/MOVE-1751881 

            Rananjay Pathania added a comment - https://getsupport.atlassian.com/browse/MOVE-1751881  

            Pallavi Biroli added a comment -

            https://getsupport.atlassian.com/browse/MOVE-1744664

            Pallavi Biroli added a comment - https://getsupport.atlassian.com/browse/MOVE-1744664

            Pallavi Biroli added a comment -

            https://getsupport.atlassian.com/browse/MOVE-1744199

            Pallavi Biroli added a comment - https://getsupport.atlassian.com/browse/MOVE-1744199

            Pallavi Biroli added a comment -

            https://getsupport.atlassian.com/browse/MOVE-1741745

            Pallavi Biroli added a comment - https://getsupport.atlassian.com/browse/MOVE-1741745

            Edwin Stol added a comment -

            You can request Atlassian Support (via a ticket) to remove the 'Migrated on' text on configuration items, they can action this via scrips on their side. We have requested this several times for our customers.

            Edwin Stol added a comment - You can request Atlassian Support (via a ticket) to remove the 'Migrated on' text on configuration items, they can action this via scrips on their side. We have requested this several times for our customers.

            Jochen Wirth added a comment - - edited

            I wondered why my manual changes on the description of customfields had no effect at all. Now I found that the (Migrated on ...) was also set in the field configurations for the projects. So I have to manually revmove alle descriptions within the fieldconfigurations for every field.... a lot of clicking

            Jochen Wirth added a comment - - edited I wondered why my manual changes on the description of customfields had no effect at all. Now I found that the (Migrated on ...) was also set in the field configurations for the projects. So I have to manually revmove alle descriptions within the fieldconfigurations for every field.... a lot of clicking

            Trudy Claspill added a comment -

            The Migrate All At Once option is not viable for my scenario.

            Trudy Claspill added a comment - The Migrate All At Once option is not viable for my scenario.

            Dwight Holman added a comment -

            Have found the "migrated" text is not added when you use the Migrate all at once pathway. If this works for your instance/migration I suggest you try it.

            Dwight Holman added a comment - Have found the "migrated" text is not added when you use the Migrate all at once pathway. If this works for your instance/migration I suggest you try it.

            Trudy Claspill added a comment -

            I did a migration using JCMA 1.9.17 with the Workaround, and it did not work.

            (Note I could not use JCMA 1.10.10 because of bugs in it related to cross-project filter and board migration, so I don't know if the Workaround works in that version.)

            Trudy Claspill added a comment - I did a migration using JCMA 1.9.17 with the Workaround, and it did not work. (Note I could not use JCMA 1.10.10 because of bugs in it related to cross-project filter and board migration, so I don't know if the Workaround works in that version.)

              103579c89d5e Shraddha Garg
              akasper André K. (Inactive)
              Votes:
              260 Vote for this issue
              Watchers:
              191 Start watching this issue

                Created:
                Updated: