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

Move RLD processing to another server

    Details

    • Sprint:
      CFAMX 2020R1 Hardening
    • SCRUM Team:
      Brotherhood of Mutants
    • Story Points:
      0
    • Work Type Classification:
      Sustaining

      Description

      As a developer, I would like to move the RLD processing to another server using the new Server Manager task configuration as a proof of concept that we are able to move load off of instance 1.

        Attachments

          Issue Links

          implements

          Feature Request - CFAMX-7492 Move RLD processing to another server

          • Major - Major loss of function.
          • Closed
          1.
          		 Review Test Scripts QA Task Done Unassigned

          0%
          Original Estimate - 0.5h
          Time Not Required
          2.
          		 Deploy QA Task Done Unassigned

          0%
          Original Estimate - 0.5h
          Time Not Required
          3.
          		 Functional Review with QA Dev Task Done Unassigned

          0%
          Original Estimate - 0.5h
          Time Not Required
          4.
          		 DIT Dev Task Done Corey Amend (Inactive)

          100%
          Original Estimate - 0.5h
          Time Spent - 1m Time Not Required

            Activity

              People

              • Assignee:
                Corey.Amend Corey Amend (Inactive)
                Reporter:
                Corey.Amend Corey Amend (Inactive)
              • Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 2h
                  2h
                  Remaining:
                  0h
                  Logged:
                  Time Not Required
                  1m

                    PagerDuty

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