Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Copy the translations of form (2.0) from one version to next version in implementer-interface

Description

As a user,
I want to see my previous version translations to the next version of a form2.0 form.
So that I don't need to write all my translations again in the new version

Description:
When a user clicks on translations in the form builder, he will be directed to adding translations page, where he can be able to add his translations to the respective concepts. Now, any time if I click on a new version of a form, the translations will be empty. I should be able to see my previous versions translations in that page. This will be useful, the user can be able to reuse his previous versions translations in his current version.

Acceptance Criteria:

  1. Translations from the last version should be copied to next version in the UI

  2. User can edit the translation from UI where required

  3. New translations will be copied to the next version

  4. Translations, when imported, should be copied in the translations files - currently, they are in draft mode when imported and on publishing, the translation files are lost

Implementation notes:

  • If we are creating a new form, the translations file will be generated for that first version.

  • while you are editing a published version, it will create a new next version of that form, currently in which the published translations are getting lost and fresh translations file is created.

  • We implement in a way that, while clicking on edit for published we are storing that published version as reference version, which will be used to fetch the reference version translations and copy to the newly created version translation file.

Openmrs Talk link: https://talk.openmrs.org/t/form-2-0-translations-are-not-carry-forwarded-to-subsequent-versions/22668

PR links:

bahmni ie apps:

implementer-interface:

 

Notes:

bahmni ie apps PR should be merged first, and then implementer-interface PR has to be merged

Attachments

4

Activity

Himabindu Thungathurty October 20, 2021 at 6:56 AM

Created a new bug card to fix the above mentioned issue

Himabindu Thungathurty October 8, 2021 at 7:49 AM
Edited

The functionality is tested for below 2 scenarios

  1. Translations should be carry forwarded if the existing form is edited and published.

For the above scenario, the translations are saved for next version of form for both english and Spanish locale as shown below.

English Locale

Spanish Locale

2. Translations should be carry forwarded if the form is downloaded from one Bahmni instance and import it in other Bahmni instance.

For this scenario, the translations are saved for next version of form for all locales except English locale.

We will create a separate card to fix the above mentioned issue and raise the PR

Himabindu Thungathurty September 24, 2019 at 5:06 PM

implementer-interface PR got merged. Below are the commit details for both the PR’s

Himabindu Thungathurty September 24, 2019 at 5:04 PM

Tested the below changes with both bahmni.ie.apps omod and implementer-interface PR. And below have been verified and good to be merged.

  1. Translations from the last version being carry forwarded to next version in the UI.

  2. When we import the form with translations and then with publishing, we could see the translations that got added as part of the form.

Sneha Bagri September 11, 2019 at 11:59 AM

bahmni ie apps PR merged.

implementer-interface : Yet to be merged.

Fixed
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Labels

UAT Assignee

Components

Sprint

Fix versions

Priority

Created July 22, 2019 at 2:05 PM
Updated October 20, 2021 at 6:57 AM
Resolved October 20, 2021 at 6:57 AM