When an issue is create as part of PWDM transmission, all the field get read only.
We would require to have a certain type of field to stay enable at any stage of a transmittal.
We would also require a field filed that can be edit on by the sender or the receiver
|
Practical use of functionality?
We have an issue that will stay open and require a fix at a later time.
Then the customer when he will review his IRS can exclude those isser knwoing they will be process later in the project |
|
|
What is the impact of not doing this?
The impact is t better communicate with the client why an issue is till open and be able to use that response to manage the open issuer. |
Hello Justina
Yes at the moment we try to make the most out of this comment field. But we feel we have limitations.
1-The field is read only once enter the comment and cannot be edit. So we need to make sure we enter the comment correctly the first time. Most team are developing the comment over a period of 10 day or +. Which involve many iteration before having the final comment, ready to be send.
2- Have not find way to display comments under IRS or how to make a search.
Example we have user that use the comment to indicate "This will be resolve at 70%" This become gray data. Meaning we cannot use it unless we open the comment or we are aware it exist.
To make an analogy, We can create a word document with lost of data, but unless we open the word, data inside Word is a gray data that is not that easily accessible.
3- We have internal discussions around an issue, that we would like to keep internal and the comment field does not allow this.
The request above is a specific, but there is a more global vision about the issue exchange and resolution
Have you considered sending this information through Issue comments field?