Details

    • Type: Sprint Defect
    • Status: Done (View Workflow)
    • Priority: Major
    • Resolution: Completed
    • Affects Version/s: CFA 2022R2
    • Fix Version/s: None
    • Component/s: Imports
    • Labels:
      None
    • SCRUM Team:
      Brotherhood of Mutants
    • Source Code ID(s):
    • Sprint:
      2022.R2 New Features Sprint 5, 2022.R3 New Features Sprint 1

      Description

      Details
      Master Operator unable to Access DFL Store

      Testing Environment Details
      Effected Server: JAT
      Build: rule.ruler4
      Affected: All
      iPad Version: 14.4.1
      Store(s): Any
      Logged in User: ape.escape / 123456

      Feature: N/A
      Related Tickets (Stories or Features): CFAMX-19319
      Other Related Links (Confluence, BRDs, Etc...): N/A
      Feature Configurations: CFAMX-18499

      Steps to Reproduce:
      1. Login to Server Manager
      2. Ensure Operator All File conttains multiple locations including DFL Store
      3. Process File
      4. Login as the Operator processed
      5. Navigate to User Settings > Change Store

       

      Expected Result
      Operator should see all stores assigned

      Actual Result
      Operator is unable to access DFL Store

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Tristan.Strong Tristan Strong
                Reporter:
                Tristan.Strong Tristan Strong
              • Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 8h
                  8h
                  Remaining:
                  0h
                  Logged:
                  Time Not Required
                  Not Specified

                    PagerDuty

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