Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Reverted from v. 12

...

Page Properties
idjirareport


Date

April 11, 2019

Issues

Jira Legacy
server

SSDT

System JIRA
jqlQueryproject = USASR AND fixVersion = v7.18.4
counttrue
serverId

925ea1db

6d21ed14-

0df8

3f48-

3e91

3cc2-

bcfb

ad28-

6b1c8a04f6ca

6548879d10d6


Summary

This is the fourth hotfix release for version 7.18.  This hotfix includes the following corrections and improvements:

  • Subject codes have been updated to allow the use of valid 2 digit subject codes (example: 05000).
  • Corrected a problem with the EIS Configuration where items were not correctly being flagged as inventory items.  The problem was found to be with the account filter associated with the EIS Configuration, it was missing the TI value as this was added to account filters later.  This prevented any of the accounts from matching the filter.  Any district that migrated before the 7.8.0 release (August 8, 2018) that is using the EIS Module will be impacted and will want to follow these directions to make sure all inventory items that meet the criteria are are properly flagged.
    • Disable the EIS Module
    • Delete the existing account filters: ssdt-eisClassicEnabledFilter &/or ssdt-eisClassicAutomaticFilter (Districts may have one or both filters)
    • Re-enable the EIS Module and be sure to edit the EIS Configuration to the desired impact
  • We've corrected a problem with remaining encumbrance that was introduced with the 7.17.1 release.  This problem is specific to disbursements that were posted in the Redesign against imported invoices.  The Encumbrance Service was posting an adjustment impact for the disbursement amount because the invoice was marked legacy.  This was causing remaining encumbrance amounts to be inflated.
  • Corrected a problem when cloning a purchase order that retained the original legacyPOStatus and legacyOutstanding values.  These fields are no longer being cloned.
  • The method that retrieves the FYTD transactions for the Budget account was modified to clear the time so it returns all transactions for the date specified.  This method is used when determining the FYTD Expendable amount.
  • Correct a problem with the 7.010 and 7.020 total lines on the Spending Plan reports.

...

Issues included on this release

Jira Legacy
serverSSDT System JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject = USASR AND fixVersion = v7.18.4
serverId925ea1db6d21ed14-0df83f48-3e913cc2-bcfbad28-6b1c8a04f6ca6548879d10d6