Skip to:

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

Make the message "No lot defined" displayed different in the table when a orderable has lot but choose "No lot defined" and a orderable has no lot choose nothing.

Description

Feedback from the ticket of 634:
Inside the table itself, when there is a product that no lots, we want the Lot Code column to use a translatable message key with a name such as "...ProductHasNoLots". The message string in English should say "No lot defined". Inside the table, these rows for products that do not have any lots would look just like the rows for products that do have a Lot where the user picked the "No lot defined" choice for the Lotless stock card. Having a different message key will allow us to change this specific message later in the future.

Attachments

1

relates to

QAlity Plus - Test Management

Checklists

Activity

Show:
Brandon Bowersox-Johnson
May 20, 2017 at 6:30 PM

Excellent! Looks good to me too.

Mary Jo Kochendorfer
May 19, 2017 at 6:45 PM

Ok. Looks good to me.

Wei Zhang
May 19, 2017 at 2:38 AM


For this ticket, we have already done, please see the attachment:

  • If the orderable has some lots but user chooses "No lot define", then it will call the first message key.

  • If the orderable has no lot, then it will call the second message key.

Let us know if you have any feedback.

Yi Deng
May 19, 2017 at 2:20 AM
Brandon Bowersox-Johnson
May 15, 2017 at 9:50 PM
(edited)

We want to use a different message key even though for now it will display the same English message, "No lot defined". We want a different message key so that we can easily differentiate the message in the future.

On the showcase meeting last week I believe was on board with this idea if you have any further questions.

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

Details

Assignee

Reporter

Labels

Components

Sprint

None

Fix versions

Priority

Parent

Time Assistant

Created May 12, 2017 at 8:03 AM
Updated February 12, 2018 at 11:30 PM
Resolved May 24, 2017 at 2:46 AM