Document Management SystemProject Type: software

Document Management System

Uploaded image for project: 'Document Management System'
  1. Document Management System
  2. DMS-43

Create chain of approval users

    Details

    • Type: New Feature
    • Status: To Do
    • Priority: Medium
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: Multiple Signer
    • Labels:

      Description

      Overview:

      Allow DMS user the ability to create a chain of users (workflow) in which a form will be sent so that each subsequent user can approve or decline a document.

      Entry Criteria:

      1. User enters DMS platform via link or consuming application.
      2. User navigates to create an approval workflow

      Acceptance Criteria:

      1. If I am a DMS user creating an approval workflow, I can enter in static people that should approve a document so that is go to specific people.
      2. If I am a DMS user creating an approval workflow, I can use a hierarchy to dynamically pull in approvers (ie. hiring manager to be pull in from ATS requisition).
      3. If I am a DMS user creating an approval workflow, I can save the workflow to be able to use when I have a document that needs approval.
      4. If I am a DMS user creating an approval workflow, I can copy a workflow so that I can tweak it and save a new workflow from the existing workflow.

      Exit Criteria:

      1. DMS user hits 'Save'.
      2. DMS user exits the DMS platform.

      Prerequisites:

      1. User is a current user of CBAT, CBES, or WT OR has stand alone link to log in.
      2. User knows how to access portal either by link or within CB application.

        Attachments

        1. 1.3 Add New Approver.png
          1.3 Add New Approver.png
          114 kB
        2. 1.1 Approver List.png
          1.1 Approver List.png
          146 kB
        3. 1.4 Add New Approver.png
          1.4 Add New Approver.png
          116 kB
        4. 1.2 Add New Approver.png
          1.2 Add New Approver.png
          95 kB
        5. 1.6 Approver List Copy.png
          1.6 Approver List Copy.png
          111 kB
        6. 1.5 Approver List actions.png
          1.5 Approver List actions.png
          147 kB

          Issue Links

          relates to

          New Feature - A new feature of the product, which has yet to be developed. DMS-1824 Create an API to fetch all approver groups along with paging and sorting features.

          • Medium - Has the potential to affect progress.
          • On hold in Test

          New Feature - A new feature of the product, which has yet to be developed. DMS-1825 Create an API to fetch particular approver group details

          • Medium - Has the potential to affect progress.
          • On hold in Test

          New Feature - A new feature of the product, which has yet to be developed. DMS-1826 Create an API to add/update approver group data.

          • Medium - Has the potential to affect progress.
          • To Do

          New Feature - A new feature of the product, which has yet to be developed. DMS-1827 Create an API to delete a particular approver group.

          • Medium - Has the potential to affect progress.
          • In QA Testing

          New Feature - A new feature of the product, which has yet to be developed. DMS-1828 Create a popup UI for adding/updating the approver group.

          • Medium - Has the potential to affect progress.
          • On hold in Test

          New Feature - A new feature of the product, which has yet to be developed. DMS-1829 Create a page to show all list of approver group along with data table functionality and action buttons

          • Medium - Has the potential to affect progress.
          • Done

            Activity

            Ascending order - Click to sort in descending order
            molly.ronovsky Molly Ronovsky (Inactive) created issue -
            molly.ronovsky Molly Ronovsky (Inactive) made changes -
            Field Original Value New Value
            Epic Link DMS-40 [ 69739 ]
            molly.ronovsky Molly Ronovsky (Inactive) made changes -
            Fix Version/s Winter release [ 10428 ]
            Prashant.samal Prashant Samal (Inactive) made changes -
            Sprint DMS - Sprint 4 [ 132 ]
            Prashant.samal Prashant Samal (Inactive) made changes -
            Rank Ranked higher
            swapnil.pandhare Swapnil Pandhare (Inactive) made changes -
            Sprint DMS - Sprint 4 [ 132 ]
            akash.thakur Akash Thakur (Inactive) made changes -
            Sprint DMS - Sprint 6 [ 134 ]
            akash.thakur Akash Thakur (Inactive) made changes -
            Rank Ranked higher
            swapnil.pandhare Swapnil Pandhare (Inactive) made changes -
            Sprint DMS - Sprint 6 [ 134 ]
            prasad.patil Prasad Patil (Inactive) made changes -
            Resolution Not in scope [ 10700 ]
            Status To Do [ 10000 ] Done [ 10001 ]
            rohan.khandave Rohan J Khandave (Inactive) made changes -
            Resolution Not in scope [ 10700 ]
            Status Done [ 10001 ] To Do [ 10000 ]
            shashikant.mishra ShashiKant Mishra (Inactive) made changes -
            Fix Version/s Enhancements - Fall [ 10610 ]
            Fix Version/s Winter release [ 10428 ]
            samir Samir made changes -
            Remaining Estimate 32h [ 115200 ]
            Original Estimate 32h [ 115200 ]
            shashikant.mishra ShashiKant Mishra (Inactive) made changes -
            Sprint DMS - Fall Sprint 6 [ 165 ]
            samir Samir made changes -
            Assignee Samir [ samir ] Robert Malony [ robert.malony ]
            shashikant.mishra ShashiKant Mishra (Inactive) made changes -
            Sprint DMS - Fall Sprint 6 [ 165 ] DMS - Fall Sprint 6, DMS - Fall Sprint 7 [ 165, 166 ]
            Robert.Malony Robert Malony (Inactive) made changes -
            Description Overview:
            Allow DMS user the ability to create a chain of users (workflow) in which a form will be sent so that each subsequent user can approve or decline a document.

            Entry:
            1. User enters DMS platform via link or consuming application.
            2. User navigates to create an approval workflow

            Acceptance Criteria:
            *IF I am a DMS user creating an approval workflow, I can enter in static people that should approve a document so that is go to specific people.
            *IF I am a DMS user creating an approval workflow, I can use a hierarchy to dynamically pull in approvers (ie. hiring manager to be pull in from ATS requisition).
            *IF I am a DMS user creating an approval workflow, I can save the workflow to be able to use when I have a document that needs approval.
            *IF I am a DMS user creating an approval workflow, I can copy a workflow so that I can tweak it and save a new workflow from the existing workflow.
             
            Exit:
            *DMS user hits 'Save'.
            *DMS user exits the DMS platform.

            Prerequisites:
            *User is a current user of CBAT, CBES, or WT OR has stand alone link to log in.
            *User knows how to access portal either by link or within CB application.             		h2. h2. Overview:
             Allow DMS user the ability to create a chain of users (workflow) in which a form will be sent so that each subsequent user can approve or decline a document.

            Entry Criteria:
             # User enters DMS platform via link or consuming application.
             # User navigates to create an approval workflow

            Acceptance Criteria:
             # IF I am a DMS user creating an approval workflow, I can enter in static people that should approve a document so that is go to specific people.
             # IF I am a DMS user creating an approval workflow, I can use a hierarchy to dynamically pull in approvers (ie. hiring manager to be pull in from ATS requisition).
            # IF I am a DMS user creating an approval workflow, I can save the workflow to be able to use when I have a document that needs approval.
             # IF I am a DMS user creating an approval workflow, I can copy a workflow so that I can tweak it and save a new workflow from the existing workflow.

            Exit Criteria:
             # DMS user hits 'Save'.
             # DMS user exits the DMS platform.

            Prerequisites:
            # User is a current user of CBAT, CBES, or WT OR has stand alone link to log in.
             # User knows how to access portal either by link or within CB application.
            Robert.Malony Robert Malony (Inactive) made changes -
            Description h2. h2. Overview:
             Allow DMS user the ability to create a chain of users (workflow) in which a form will be sent so that each subsequent user can approve or decline a document.

            Entry Criteria:
             # User enters DMS platform via link or consuming application.
             # User navigates to create an approval workflow

            Acceptance Criteria:
             # IF I am a DMS user creating an approval workflow, I can enter in static people that should approve a document so that is go to specific people.
             # IF I am a DMS user creating an approval workflow, I can use a hierarchy to dynamically pull in approvers (ie. hiring manager to be pull in from ATS requisition).
            # IF I am a DMS user creating an approval workflow, I can save the workflow to be able to use when I have a document that needs approval.
             # IF I am a DMS user creating an approval workflow, I can copy a workflow so that I can tweak it and save a new workflow from the existing workflow.

            Exit Criteria:
             # DMS user hits 'Save'.
             # DMS user exits the DMS platform.

            Prerequisites:
            # User is a current user of CBAT, CBES, or WT OR has stand alone link to log in.
             # User knows how to access portal either by link or within CB application.             		Overview:

            Allow DMS user the ability to create a chain of users (workflow) in which a form will be sent so that each subsequent user can approve or decline a document.

             

            Entry Criteria:
             # User enters DMS platform via link or consuming application.
             # User navigates to create an approval workflow

             

            Acceptance Criteria:
             # IF I am a DMS user creating an approval workflow, I can enter in static people that should approve a document so that is go to specific people.
             # IF I am a DMS user creating an approval workflow, I can use a hierarchy to dynamically pull in approvers (ie. hiring manager to be pull in from ATS requisition).
             # IF I am a DMS user creating an approval workflow, I can save the workflow to be able to use when I have a document that needs approval.
             # IF I am a DMS user creating an approval workflow, I can copy a workflow so that I can tweak it and save a new workflow from the existing workflow.

             

            Exit Criteria:
             # DMS user hits 'Save'.
             # DMS user exits the DMS platform.

             

            Prerequisites:
             # User is a current user of CBAT, CBES, or WT OR has stand alone link to log in.
             # User knows how to access portal either by link or within CB application.
            Robert.Malony Robert Malony (Inactive) made changes -
            Description Overview:

            Allow DMS user the ability to create a chain of users (workflow) in which a form will be sent so that each subsequent user can approve or decline a document.

             

            Entry Criteria:
             # User enters DMS platform via link or consuming application.
             # User navigates to create an approval workflow

             

            Acceptance Criteria:
             # IF I am a DMS user creating an approval workflow, I can enter in static people that should approve a document so that is go to specific people.
             # IF I am a DMS user creating an approval workflow, I can use a hierarchy to dynamically pull in approvers (ie. hiring manager to be pull in from ATS requisition).
             # IF I am a DMS user creating an approval workflow, I can save the workflow to be able to use when I have a document that needs approval.
             # IF I am a DMS user creating an approval workflow, I can copy a workflow so that I can tweak it and save a new workflow from the existing workflow.

             

            Exit Criteria:
             # DMS user hits 'Save'.
             # DMS user exits the DMS platform.

             

            Prerequisites:
             # User is a current user of CBAT, CBES, or WT OR has stand alone link to log in.
             # User knows how to access portal either by link or within CB application.             		h2. Overview:
            Allow DMS user the ability to create a chain of users (workflow) in which a form will be sent so that each subsequent user can approve or decline a document.

             h3. Entry Criteria:
             # User enters DMS platform via link or consuming application.
             # User navigates to create an approval workflow

             h3. Acceptance Criteria:
             # IF I am a DMS user creating an approval workflow, I can enter in static people that should approve a document so that is go to specific people.
             # IF I am a DMS user creating an approval workflow, I can use a hierarchy to dynamically pull in approvers (ie. hiring manager to be pull in from ATS requisition).
             # IF I am a DMS user creating an approval workflow, I can save the workflow to be able to use when I have a document that needs approval.
             # IF I am a DMS user creating an approval workflow, I can copy a workflow so that I can tweak it and save a new workflow from the existing workflow.

             h3. Exit Criteria:
             # DMS user hits 'Save'.
             # DMS user exits the DMS platform.

             h3. Prerequisites:
             # User is a current user of CBAT, CBES, or WT OR has stand alone link to log in.
             # User knows how to access portal either by link or within CB application.
            Robert.Malony Robert Malony (Inactive) made changes -
            Description h2. Overview:
            Allow DMS user the ability to create a chain of users (workflow) in which a form will be sent so that each subsequent user can approve or decline a document.

             h3. Entry Criteria:
             # User enters DMS platform via link or consuming application.
             # User navigates to create an approval workflow

             h3. Acceptance Criteria:
             # IF I am a DMS user creating an approval workflow, I can enter in static people that should approve a document so that is go to specific people.
             # IF I am a DMS user creating an approval workflow, I can use a hierarchy to dynamically pull in approvers (ie. hiring manager to be pull in from ATS requisition).
             # IF I am a DMS user creating an approval workflow, I can save the workflow to be able to use when I have a document that needs approval.
             # IF I am a DMS user creating an approval workflow, I can copy a workflow so that I can tweak it and save a new workflow from the existing workflow.

             h3. Exit Criteria:
             # DMS user hits 'Save'.
             # DMS user exits the DMS platform.

             h3. Prerequisites:
             # User is a current user of CBAT, CBES, or WT OR has stand alone link to log in.
             # User knows how to access portal either by link or within CB application.             		h2. Overview:
            Allow DMS user the ability to create a chain of users (workflow) in which a form will be sent so that each subsequent user can approve or decline a document.

            h3. Entry Criteria:
             # User enters DMS platform via link or consuming application.
             # User navigates to create an approval workflow

            h3. Acceptance Criteria:
            # IF I am a DMS user creating an approval workflow, I can enter in static people that should approve a document so that is go to specific people.
            # IF I am a DMS user creating an approval workflow, I can use a hierarchy to dynamically pull in approvers (ie. hiring manager to be pull in from ATS requisition).
            # IF I am a DMS user creating an approval workflow, I can save the workflow to be able to use when I have a document that needs approval.
             # IF I am a DMS user creating an approval workflow, I can copy a workflow so that I can tweak it and save a new workflow from the existing workflow.

            h3. Exit Criteria:
             # DMS user hits 'Save'.
             # DMS user exits the DMS platform.

            h3. Prerequisites:
            # User is a current user of CBAT, CBES, or WT OR has stand alone link to log in.
            # User knows how to access portal either by link or within CB application.
            Robert.Malony Robert Malony (Inactive) made changes -
            Description h2. Overview:
            Allow DMS user the ability to create a chain of users (workflow) in which a form will be sent so that each subsequent user can approve or decline a document.

            h3. Entry Criteria:
             # User enters DMS platform via link or consuming application.
             # User navigates to create an approval workflow

            h3. Acceptance Criteria:
            # IF I am a DMS user creating an approval workflow, I can enter in static people that should approve a document so that is go to specific people.
            # IF I am a DMS user creating an approval workflow, I can use a hierarchy to dynamically pull in approvers (ie. hiring manager to be pull in from ATS requisition).
            # IF I am a DMS user creating an approval workflow, I can save the workflow to be able to use when I have a document that needs approval.
             # IF I am a DMS user creating an approval workflow, I can copy a workflow so that I can tweak it and save a new workflow from the existing workflow.

            h3. Exit Criteria:
             # DMS user hits 'Save'.
             # DMS user exits the DMS platform.

            h3. Prerequisites:
            # User is a current user of CBAT, CBES, or WT OR has stand alone link to log in.
            # User knows how to access portal either by link or within CB application.             		h2. Overview:
            Allow DMS user the ability to create a chain of users (workflow) in which a form will be sent so that each subsequent user can approve or decline a document.

            h3. Entry Criteria:
            # User enters DMS platform via link or consuming application.
            # User navigates to create an approval workflow

            h3. Acceptance Criteria:
            # IF I am a DMS user creating an approval workflow, I can enter in static people that should approve a document so that is go to specific people.
            # IF I am a DMS user creating an approval workflow, I can use a hierarchy to dynamically pull in approvers (ie. hiring manager to be pull in from ATS requisition).
            # IF I am a DMS user creating an approval workflow, I can save the workflow to be able to use when I have a document that needs approval.
             # IF I am a DMS user creating an approval workflow, I can copy a workflow so that I can tweak it and save a new workflow from the existing workflow.

            h3. Exit Criteria:
            # DMS user hits 'Save'.
            # DMS user exits the DMS platform.

            h3. Prerequisites:
            # User is a current user of CBAT, CBES, or WT OR has stand alone link to log in.
            # User knows how to access portal either by link or within CB application.
            Robert.Malony Robert Malony (Inactive) made changes -
            Description h2. Overview:
            Allow DMS user the ability to create a chain of users (workflow) in which a form will be sent so that each subsequent user can approve or decline a document.

            h3. Entry Criteria:
            # User enters DMS platform via link or consuming application.
            # User navigates to create an approval workflow

            h3. Acceptance Criteria:
            # IF I am a DMS user creating an approval workflow, I can enter in static people that should approve a document so that is go to specific people.
            # IF I am a DMS user creating an approval workflow, I can use a hierarchy to dynamically pull in approvers (ie. hiring manager to be pull in from ATS requisition).
            # IF I am a DMS user creating an approval workflow, I can save the workflow to be able to use when I have a document that needs approval.
             # IF I am a DMS user creating an approval workflow, I can copy a workflow so that I can tweak it and save a new workflow from the existing workflow.

            h3. Exit Criteria:
            # DMS user hits 'Save'.
            # DMS user exits the DMS platform.

            h3. Prerequisites:
            # User is a current user of CBAT, CBES, or WT OR has stand alone link to log in.
            # User knows how to access portal either by link or within CB application.             		h2. Overview:
            Allow DMS user the ability to create a chain of users (workflow) in which a form will be sent so that each subsequent user can approve or decline a document.

            h3. Entry Criteria:
            # User enters DMS platform via link or consuming application.
            # User navigates to create an approval workflow

            h3. Acceptance Criteria:
            # If I am a DMS user creating an approval workflow, I can enter in static people that should approve a document so that is go to specific people.
            # If I am a DMS user creating an approval workflow, I can use a hierarchy to dynamically pull in approvers (ie. hiring manager to be pull in from ATS requisition).
            # If I am a DMS user creating an approval workflow, I can save the workflow to be able to use when I have a document that needs approval.
            # If I am a DMS user creating an approval workflow, I can copy a workflow so that I can tweak it and save a new workflow from the existing workflow.

            h3. Exit Criteria:
            # DMS user hits 'Save'.
            # DMS user exits the DMS platform.

            h3. Prerequisites:
            # User is a current user of CBAT, CBES, or WT OR has stand alone link to log in.
            # User knows how to access portal either by link or within CB application.
            Robert.Malony Robert Malony (Inactive) made changes -
            Labels Needs_UX
            Robert.Malony Robert Malony (Inactive) made changes -
            Assignee Robert Malony [ robert.malony ] Kristen [ ruel ]
            aruna.raheja Aruna Raheja made changes -
            Attachment 1.1 Approver List.png [ 113200 ]
            Attachment 1.2 Add New Approver.png [ 113201 ]
            Attachment 1.3 Add New Approver.png [ 113202 ]
            Attachment 1.4 Add New Approver.png [ 113203 ]
            Attachment 1.5 Approver List actions.png [ 113204 ]
            Attachment 1.6 Approver List Copy.png [ 113205 ]
            shashikant.mishra ShashiKant Mishra (Inactive) made changes -
            Sprint DMS - Fall Sprint 6, DMS - Fall Sprint 7 [ 165, 166 ] DMS - Fall Sprint 6, DMS - Fall Sprint 7, DMS - Fall Sprint 8 [ 165, 166, 167 ]
            aruna.raheja Aruna Raheja made changes -
            Attachment 1.3 Add New Approver.png [ 113202 ]
            aruna.raheja Aruna Raheja made changes -
            Attachment 1.4 Add New Approver.png [ 113203 ]
            aruna.raheja Aruna Raheja made changes -
            Attachment 1.2 Add New Approver.png [ 113201 ]
            aruna.raheja Aruna Raheja made changes -
            Attachment 1.1 Approver List.png [ 113200 ]
            aruna.raheja Aruna Raheja made changes -
            Attachment 1.5 Approver List actions.png [ 113204 ]
            aruna.raheja Aruna Raheja made changes -
            Attachment 1.6 Approver List Copy.png [ 113205 ]
            aruna.raheja Aruna Raheja made changes -
            Attachment 1.1 Approver List.png [ 114000 ]
            Attachment 1.2 Add New Approver.png [ 114001 ]
            Attachment 1.3 Add New Approver.png [ 114002 ]
            Attachment 1.4 Add New Approver.png [ 114003 ]
            Attachment 1.5 Approver List actions.png [ 114004 ]
            Attachment 1.6 Approver List Copy.png [ 114005 ]
            aruna.raheja Aruna Raheja made changes -
            Attachment 1.5 Approver List actions.png [ 114004 ]
            aruna.raheja Aruna Raheja made changes -
            Attachment 1.5 Approver List actions.png [ 114818 ]
            samir Samir made changes -
            Fix Version/s Between Fall and Winter 2019 [ 10919 ]
            Fix Version/s Enhancements - Fall [ 10610 ]
            samir Samir made changes -
            Sprint DMS - Fall Sprint 6, DMS - Fall Sprint 7, DMS - Fall Sprint 8 [ 165, 166, 167 ] DMS - Fall Sprint 6, DMS - Fall Sprint 7 [ 165, 166 ]
            shashikant.mishra ShashiKant Mishra (Inactive) made changes -
            Sprint DMS - Fall Sprint 6, DMS - Fall Sprint 7 [ 165, 166 ] DMS - Fall Sprint 6, DMS - Fall Sprint 7, DMS - Fall release wrap - 1 [ 165, 166, 173 ]
            shashikant.mishra ShashiKant Mishra (Inactive) made changes -
            Rank Ranked lower
            shashikant.mishra ShashiKant Mishra (Inactive) made changes -
            Sprint DMS - Fall Sprint 6, DMS - Fall Sprint 7, DMS - Gap Fall & Win Sprint 1 [ 165, 166, 173 ] DMS - Fall Sprint 6, DMS - Fall Sprint 7, DMS - Gap Fall & Win Sprint 1, DMS - Gap Fall & Win Sprint 2 [ 165, 166, 173, 174 ]
            samir Samir made changes -
            Sprint DMS - Fall Sprint 6, DMS - Fall Sprint 7, DMS - Gap Fall & Win Sprint 1, DMS - Gap Fall & Win Sprint 2 [ 165, 166, 173, 174 ] DMS - Fall Sprint 6, DMS - Fall Sprint 7, DMS - Gap Fall & Win Sprint 1, DMS - Gap Fall & Win Sprint 3 [ 165, 166, 173, 177 ]
            shashikant.mishra ShashiKant Mishra (Inactive) made changes -
            Original Estimate 32h [ 115200 ] 64h [ 230400 ]
            samir Samir made changes -
            Assignee Kristen [ ruel ] Narendra Kumar [ narendra.kumar ]
            samir Samir made changes -
            Sprint DMS - Fall Sprint 6, DMS - Fall Sprint 7, DMS - Gap Fall & Win Sprint 1, DMS - Gap Fall & Win Sprint 3 [ 165, 166, 173, 177 ] DMS - Fall Sprint 6, DMS - Fall Sprint 7, DMS - Gap Fall & Win Sprint 1, DMS - Gap Fall & Win Sprint 4 [ 165, 166, 173, 179 ]
            narendra.kumar Narendra Kumar made changes -
            Fix Version/s Winter 2020 Multiple Signers [ 11313 ]
            Fix Version/s Between Fall and Winter 2019 [ 10919 ]
            narendra.kumar Narendra Kumar made changes -
            Sprint DMS - Fall Sprint 6, DMS - Fall Sprint 7, DMS - Gap Fall & Win Sprint 1, DMS - Gap Fall & Win Sprint 4 [ 165, 166, 173, 179 ] DMS - Fall Sprint 6, DMS - Fall Sprint 7, DMS - Gap Fall & Win Sprint 1 [ 165, 166, 173 ]
            narendra.kumar Narendra Kumar made changes -
            Link This issue relates to DMS-1824 [ DMS-1824 ]
            narendra.kumar Narendra Kumar made changes -
            Link This issue relates to DMS-1825 [ DMS-1825 ]
            narendra.kumar Narendra Kumar made changes -
            Link This issue relates to DMS-1826 [ DMS-1826 ]
            narendra.kumar Narendra Kumar made changes -
            Link This issue relates to DMS-1827 [ DMS-1827 ]
            narendra.kumar Narendra Kumar made changes -
            Link This issue relates to DMS-1828 [ DMS-1828 ]
            narendra.kumar Narendra Kumar made changes -
            Link This issue relates to DMS-1829 [ DMS-1829 ]
            narendra.kumar Narendra Kumar made changes -
            Link This issue relates to DMS-1826 [ DMS-1826 ]
            narendra.kumar Narendra Kumar made changes -
            Link This issue relates to DMS-1826 [ DMS-1826 ]
            narendra.kumar Narendra Kumar made changes -
            Fix Version/s Multiple Signer [ 12111 ]
            Fix Version/s Winter 2020 Multiple Signers [ 11313 ]

              People

              Assignee:
              narendra.kumar Narendra Kumar
              Reporter:
              molly.ronovsky Molly Ronovsky (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:

                  Time Tracking

                  Estimated:
                  Original Estimate - 64h
                  64h
                  Remaining:
                  Remaining Estimate - 32h
                  32h
                  Logged:
                  Time Spent - Not Specified Time Not Required
                  Not Specified