Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Add functionality status modal to the CCE inventory item list

Description

Acceptance Criteria:

  • UI for Functionality Status modal follows attached mockup

  • Each line contains a button for "Update status"

    • next to the displayed Functionality status value should be an Edit icon button

    • the button should only be visible if user has right yo edit

  • Clicking the Edit icon button brings up a modal for Update Functionality Status.

  • For the Update Functionality Status modal, the following should be true:

    • The title of the modal should be "Equipment Functional Status"

    • The text above the Update Status section should have the equipment's <Reference name> as the header (this is a new field that we are adding in https://openlmis.atlassian.net/browse/OLMIS-2619#icft=OLMIS-2619

    • The <facility name> should appear under a "Facility" subheading beneath the <Reference name> header (the same way you have <equipment type> appearing)

    • Make/model and serial number do not need to appear in this modal

    • Select options for Functionality Status are: Functioning, Nonfunctioning, Obsolete

    • Select options for Reasons for Not Working are: Awaiting repair, Needs spare parts, Unservicable, No finance, No fuel, Surplus, Dead, Not applicable

    • For all functionality statuses EXCEPT "Functioning," Reason for not working is required.

    • If Functionality Status is "Functioning," options for Reasons for not working should be hidden

    • If Functionality Status is "Obsolete," the field Year of decommission is also required

    • Year of decommission should be a 4-digit numeral calendar selection

    • For all functionality statuses EXCEPT "Obsolete," Date of decommission should be hidden

    • Test case is created in Zephyr for this scenario, and test case is linked to this ticket

Attachments

10

Confluence content

mentioned on

QAlity Plus - Test Management

Checklists

Activity

Show:
Mateusz Kwiatkowski
August 22, 2017 at 3:53 PM

Here is video showcase for this ticket and the OLMIS-2619: https://youtu.be/W85akZC082A

Paweł Gesek
August 21, 2017 at 5:04 PM

do we have a videos showcase for this? If not list the showcase steps

Joanna Bebak
August 21, 2017 at 12:45 PM

I made a re-test, and now everything works correctly.

Rachel Powers
August 18, 2017 at 7:37 PM

#4 #5 Hi , sorry for the confusion. We had to move some of the Functional Statuses from before into the Reasons for not functioning status. The correct Functional Statuses are listed in above in the AC. Awaiting_Repair and Unservicable should be Reasons for not functioning. I don't think it matters what we do with capitalization and how it appears--can we just have it match everything else?

#11 "Requires attention" is something we're going to wait on, so that's why it's not in the mockup. We can remove it.

#12 We discussed this with and last Thursday on Slack and on Skype. Looks like the change wasn't made to the AC though. We decided that using our calendar date tool for this (rather than just 4-digit year) is best. There is additional logic that we're going to have to build in regarding decommission date and status at a later date, so I think we can wait on logic for choosing a future date. (For now we'll just let the user choose a future date if they really want to.)

Sam Im
August 18, 2017 at 6:38 PM

I agree, I think the dates should be left aligned.

Done
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Labels

Story Points

Original estimate

Time tracking

1w 1d 2h 30m logged

Components

Sprint

None

Fix versions

Priority

Parent

Time Assistant

Created July 21, 2017 at 2:23 PM
Updated November 20, 2020 at 8:23 PM
Resolved August 22, 2017 at 3:53 PM