Issues with the CHANGE functionality.
We are now getting to the point where we would like to start using the change tab for managing our change requests. However, thus far I have found the following issues on build 7011 on MSSQL:
1. If there are attachments on the backout plan, rollout plan or even on the description of the change, a user who receives the approval mail from within the approvals tab, can not open said attachments.
2. The status of a new change is automatically set to Approved" when CAB members are added. This is despite the fact that no CAB members have actually approved the change.
This could lead to a change being rolled out before all CAB members have checked/approved the change.
Can anyone explain how to overcome these two issues (there very well be more in the near future)?
1. If there are attachments on the backout plan, rollout plan or even on the description of the change, a user who receives the approval mail from within the approvals tab, can not open said attachments.
2. The status of a new change is automatically set to Approved" when CAB members are added. This is despite the fact that no CAB members have actually approved the change.
This could lead to a change being rolled out before all CAB members have checked/approved the change.
Can anyone explain how to overcome these two issues (there very well be more in the near future)?