[
https://issues.apache.org/jira/browse/OFBIZ-7335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15328967#comment-15328967 ]
Pranay Pandey edited comment on OFBIZ-7335 at 6/14/16 5:22 AM:
---------------------------------------------------------------
Hi [~amardeepsj], [~pfm.smits]
Thinking of below given scenarios I think we should make this improvement suggested by Amardeep-
# At any stage user should be able to add new parties to production run as needed with required thrudate.
# At any stage based on any runtime execution plan change, user should be able to change the thruDate assigned to a partyAssignment.
The reason we need it, can be like, there may be unavailability of a party who was assigned to a production run or task, and now we need to reassign it to someone else.
In current implementation, it's not possible. As of now you can have one party assigned and now you can't reassign it to other party as the assignment can't be changed by setting thru date for the first one. Only new assignments can be added. None of these can be expired.
This case will also arise when we have longer production runs may be for 3 days, now one party started it and the other day not available for the job, other party needs to take over. This scenario can't be handled. Again now may be on 3rd day first party returned and we want to reassign the job back to him, as now we can't do that.
My 2 Cents.
was (Author: pandeypranay):
Hi [~amarouni], [~pfm.smits]
Thinking of below given scenarios I think we should make this improvement suggested by Amardeep-
# At any stage user should be able to add new parties to production run as needed with required thrudate.
# At any stage based on any runtime execution plan change, user should be able to change the thruDate assigned to a partyAssignment.
The reason we need it, can be like, there may be unavailability of a party who was assigned to a production run or task, and now we need to reassign it to someone else.
In current implementation, it's not possible. As of now you can have one party assigned and now you can't reassign it to other party as the assignment can't be changed by setting thru date for the first one. Only new assignments can be added. None of these can be expired.
This case will also arise when we have longer production runs may be for 3 days, now one party started it and the other day not available for the job, other party needs to take over. This scenario can't be handled. Again now may be on 3rd day first party returned and we want to reassign the job back to him, as now we can't do that.
My 2 Cents.
> Production run party assignment's thruDate should be editable
> -------------------------------------------------------------
>
> Key: OFBIZ-7335
> URL:
https://issues.apache.org/jira/browse/OFBIZ-7335> Project: OFBiz
> Issue Type: Improvement
> Components: manufacturing
> Affects Versions: Trunk
> Reporter: Amardeep Singh Jhajj
> Assignee: Amardeep Singh Jhajj
> Attachments: OFBIZ-7335.patch
>
>
> Currently, we don't have support to set thruDate for production run party assignment. So, there should be a support of setting the thruDate if needed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Locked
