Uploaded image for project: 'CFA MX '
  1. CFA MX
  2. CFAMX-13997

Auto Notifications - Duplicate Verification and Language Dropdown

    Details

    • Type: Story
    • Status: Closed (View Workflow)
    • Resolution: Won't Develop
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • SCRUM Team:
      Brotherhood of Mutants
    • Work Type Classification:
      Sustaining

      Description

      Story

      As a platform that supports multiple languages, I would like to prevent the accidental creation of duplicate auto notifications.

      Details

      1. CFAMX-13992 Create a new "Language" dropdown in MMS Auto Notifications.
        1. This will allow us to create new translated version of existing auto notifications.
      2. CFAMX-13997 (This Story) Update the existing validation include to "Language" when we check for duplicate Auto Notifications on "save".
      3. Send the right notification to the contact based on the store language setting and the "Language" configured in the auto notification.

      Check for Duplicate Auto Notifications When the User Saves

      In order to prevent duplicate auto notifications, we need to add the language option to the existing validation. I've tested a few things and I can't quite nail down what the exact validation combination is. It looks like the user can't save an auto notification if one already exists with the attributes listed below but I need a little help to confirm this.

      • Title
      • Type
      • Contact
      • "Subject" selection AND "Message" selection
        • System Generated
        • As Below

      Example

      Acceptance Criteria

      1. We have to make sure that we can't accidently create duplicate auto notifications as we create the translated versions.
        1. For all "Contact" options EXCEPT "As Below"
          1. When the user clicks "Update" after editing an existing or creating a new auto notification, check to see if a notification already exists that matches the one the user is attempting to create.
            1. If a duplicate auto notification exists, display Language Selection Already Exists in red below the language option.
            2. The auto notification does not save in this state.
            3. When the user selects a different language and makes the auto notification unique, the notification is saved.
            4. With the language validation in place, if the user changes an attribute other than language thereby making the notification unique, the notification is saved.
      1. For the "As Below" "Contact" Option
        1. When the user clicks "Update" at the end of editing an existing or creating a new auto notification, check to see if a notification already exists with a matching "Type", "Language", and an exact match for "Email" OR "Mobile".
          1. If an auto notification exists where all of these criteria match the notification in progress, display Language Selection Already Exists in red below the language option.
          2. When the user selects a different language and doing this makes the auto notification unique, the notification is saved.

      Sending the Auto Notification in the Right Language

      1. Once an auto notification is configured, we have to make sure we are sending the right version to the right user.

        Attachments

          Issue Links

          1.
          Review Test Scripts QA Task Ready for QA Unassigned

          0%

          Original Estimate - 0.5h
          Remaining Estimate - 0.5h
          2.
          Deploy QA Task Ready for QA Unassigned

          0%

          Original Estimate - 0.5h
          Remaining Estimate - 0.5h
          3.
          Functional Review with QA Dev Task Ready for Developer Unassigned

          0%

          Original Estimate - 0.5h
          Remaining Estimate - 0.5h
          4.
          DIT Dev Task Ready for Developer Unassigned

          0%

          Original Estimate - 0.5h
          Remaining Estimate - 0.5h

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                jason.powell Jason Powell
              • Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 2h
                  2h
                  Remaining:
                  Remaining Estimate - 2h
                  2h
                  Logged:
                  Time Spent - Not Specified
                  Not Specified

                    PagerDuty

                    Error rendering 'com.pagerduty.jira-server-plugin:PagerDuty'. Please contact your Jira administrators.