Details

    • Sub-task
    • Status: Closed (View Workflow)
    • TBD
    • Resolution: Duplicate
    • None
    • None
    • None
    • None

    Description

      In the Agreement edit pane, where a license is linked to an Agreement we should display all the Amendments that are attached to the License.

      NEEDS REVIEW BY THE DEVELOPMENT TEAM FOR FEASIBILITY

      UXPROD-1999 proposes that:

      • The value of the license field "Status (this agreement)" controls which accordion the License appears in on the Agreement preview pane: one of "Controlling license", "Future license" or "Historical license".
      • For the controlling license, the value of the amendment field "Status (this agreement)" controls which sub-heading the Amendment appears in on the Agreement preview pane: one of "Current amendments", "Future amendments" or "Historical amendments".

      This is necessary to allow the all important "Controlling license" and the amendments which are relevant to the agreement, to be separated out from future and historical licenses.

      Is this approach viable? It means that in the Edit pane the accordions and sub-headings are irrelevant and hence all are displayed under a single heading/accordion "Licenses".


      For each amendment belonging to a license:

      1. the user can:

      • Set the field "Status (this agreement)" as described in UXPROD-1997
      • Add text to the field "Amendment note". Note that this applies only in the context of the link between the Agreement -> License -> Amendment - it is not a general note on the amendment.

      2. three fields from the amendment record are displayed:

      • Status
      • Start date
      • End date

      See the mockup for an example of a license and its amendments in the agreement Edit pane.

      TestRail: Results

        Attachments

          Issue Links

            Activity

              People

                Unassigned Unassigned
                ostephens Owen Stephens
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases