Victor Posted April 19, 2017 Share Posted April 19, 2017 @Awalker looking into this...don't think you done something incorrectly, it seems to be an issue on our side... EDIT: the issue seems to be here somewhere (screenshot)... again, nothing wrong on your side but it seems the BP is having a hissy fit with the timeline updates... from the task completion and the second timeline update ("Implemented" one). May I ask, if possible, to do a test as follows: with current process raise a test CR and progress all the way to this... I think the issue should replicate at this stage; amend the process and temporarily remove the "Update Timeline - Implemented" node (eventually create a backup of current process to revert back to it); with amended process raise another test CR and progress it... I'm curious if the issue will occur again. 1 Link to comment Share on other sites More sharing options...
Awalker Posted April 19, 2017 Author Share Posted April 19, 2017 @Victor I will get onto this this afternoon, and feedback. Many thanks Link to comment Share on other sites More sharing options...
Awalker Posted April 19, 2017 Author Share Posted April 19, 2017 HI @Victor, This is odd, I have re-raised a CR using the original process, but pointed it to my test team instead of the Change management team and it worked absolutely fine. I have since removed that node ad added a stage checkpoint and re-raised a CR and again it worked fine. Link to comment Share on other sites More sharing options...
Victor Posted April 19, 2017 Share Posted April 19, 2017 @Awalker try with the original steps... by the way I know what the error is and I think dev team can fix this, I just wanted to make sure I understand the circumstances on which this occurs... Link to comment Share on other sites More sharing options...
Awalker Posted April 19, 2017 Author Share Posted April 19, 2017 Hi @Victor, Oddly i am unable to replicate the issue now, I have gone back to the original process and it seems to be working 100%. Link to comment Share on other sites More sharing options...
Victor Posted April 19, 2017 Share Posted April 19, 2017 @Awalker no worries, like I said I know what the error is and will ask dev to make sure we cater for in case it might happen again... Link to comment Share on other sites More sharing options...
Awalker Posted April 19, 2017 Author Share Posted April 19, 2017 @Victor Thank you for all your help on this, greatly appreciated. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now