Uploaded image for project: 'OpenMRS Core'
  1. OpenMRS Core
  2. TRUNK-4525

Order.isDiscontinued and Order.isCurrent should be consistent with OrderService.getActiveOrders

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Must
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: Platform 1.10.1
    • Component/s: Order Entry
    • Labels:
      None
    • Complexity:
      Low

      Description

      When one calls Order.isDiscontinued(..) and Order.isCurrent(..) on orders returned by OrderService.getActiveOrders(..), they may get back true and false respectively which is contradictory, if an order was stopped/retired on a given date, it is considered to be active as of that date but the logic Order.isDiscontinued and Order.isCurrent behaves differently.

      Same for activation date, these methods need to consider an order to be active as of that date

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                wyclif Wyclif Luyima
                Reporter:
                wyclif Wyclif Luyima
                Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    Time Tracking

                    Estimated:
                    Original Estimate - 4 hours
                    4h
                    Remaining:
                    Remaining Estimate - 0 minutes
                    0m
                    Logged:
                    Time Spent - 4 hours
                    4h