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

2022R1 Patchback CLONE - Suggested Count Report > Update Filename

    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 user, I would like each filename created when this export is run to be unique.

      Details

      Right now the filename for this export is always the same. This is confusing as the user can't tell if the file is new data or old data. To fix this we should add a timestamp to the file name when the export is generated.

      AC

      1. The filename includes a generated date and time timestamp when the export is created via the server manager
      2. The filename includes a generated date and time timestamp when the export is generated via MxC.

        Attachments

          Issue Links

          1.
          Create Test Scripts QA Task Ready for QA Unassigned

          0%

          Original Estimate - 0.5h
          Remaining Estimate - 0.5h
          2.
          Review Test Scripts QA Task Ready for QA Unassigned

          0%

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

          0%

          Original Estimate - 0.5h
          Remaining Estimate - 0.5h
          4.
          Execute Test Cases QA Task Ready for QA Unassigned

          0%

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

          0%

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

          0%

          Original Estimate - 0.5h
          Remaining Estimate - 0.5h
          7.
          Design Review Dev Task Ready for Developer Unassigned

          0%

          Original Estimate - 0.5h
          Remaining Estimate - 0.5h
          8.
          Story Documentation 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 - 4h
                  4h
                  Remaining:
                  Remaining Estimate - 4h
                  4h
                  Logged:
                  Time Spent - Not Specified
                  Not Specified

                    PagerDuty

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