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

Signal Integration -> Transfers -> Reject the API Calls for Non Signal Stores

    Details

    • Type: Story
    • Status: Closed (View Workflow)
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Sprint:
      2023.R2 Signal Int. Sprint 3
    • SCRUM Team:
      Globogym Purple Cobras
    • Story Points:
      3
    • Work Type Classification:
      Sustaining

      Description

      Story

      As a developer, I would like to reject the API calls being made to Transfer API enpoints for non signal stores. 

       

      Description

       

      AC

      Confirm that if the Transfer Create api call is being made for a non signal stores then reject it

      Confirm that if the Transfer Create api call is being made for a signal stores then we should proceed

      Confirm that if the Transfer Update api call is being made for a non signal stores then reject it

      Confirm that if the Transfer Update api call is being made for a signal stores then we should proceed

        Attachments

          Issue Links

          There are no Sub-Tasks for this issue.

            Activity

              People

              • Assignee:
                caner.saritac Caner Saritac
                Reporter:
                caner.saritac Caner Saritac
              • Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 11h
                  11h
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 10.5h Time Not Required
                  10.5h

                    PagerDuty

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