...
Is it planned that the value of the field “Expected receipt date” field in the app Orders is entered automatically when the order is opened and calculated by adding the value of the field “Expected receipt interval” in the app Organization to the date when the order is opened?
According to
the function is planned, but probably not yet available in Snapshot?Jira Legacy server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UIOR-396 JR: If the story is closed, it should be fully implemented and functional. I will review with ThunderjetClaiming is based on “receiving title” information in the Receiving app. When creating a piece in Receiving, the default expected date is the “expected receipt date” in the POL. With serials/ongoing orders, this expected date applies to the first date.
For serials with (more or less) predictable expected dates, the Serials app can be used to create receiving pieces with expected dates in the Receiving app.
For a piece to be set to “Late” in Receiving, “Claim active” must be true in the order line AND the receiving piece must have an expected date.
“Expected receipt interval” currently does not interact with other fields, and is merely informational. It can be used to estimate expected dates for receiving pieces, but the Serials app is where automatic predicting happens.
How is the value in the field “Claiming interval” in the app Orders applied?
Will the value be imported from the app Organizations for each order?
JR: The default Claiming interval from Organizations should be applied to each order line, but can be changed at the order line level.
When/How is the checkbox “Claiming active” activated?
Is the checkbox activated manually or automatically?
JR: It is activated manually
Can a default value be defined, as envisaged in
?Jira Legacy server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UIOR-397 JR: It should be configurable in templates
...