Martyn Houghton Posted February 4, 2020 Share Posted February 4, 2020 Can I have an update on defect PM00157953 in relation to "Timesheet entries are not saved when updating a request with time spent", which was identified in October 2019. We are trying to records time spent against all our requests in Service Manager to allow analysis of effort and support ability of different products, but having inconsistent saving of time spent is meaning this data is incomplete. Thanks. Martyn Link to comment Share on other sites More sharing options...
J_Tamburrini Posted February 4, 2020 Share Posted February 4, 2020 +1 we noticed this when testing first time today, the clock was disappearing from the request. 1 Link to comment Share on other sites More sharing options...
Martyn Houghton Posted March 20, 2020 Author Share Posted March 20, 2020 @James Ainsworth @Steven Boardman Could you look at raising the priority of PM00157953, as not being able to reliable record time against Service Manager actions make the use of Time sheets un-workable as a means of tracking analyst time. Cheers Martyn Link to comment Share on other sites More sharing options...
James Ainsworth Posted March 20, 2020 Share Posted March 20, 2020 Hi Martyn, I'm not familiar with the issue. The mentioned reference PM00157953 was actually closed as a solution was provided by one of our development teams last month. I take it that you are still experiencing issues? If that is the case, I'll ask them to have another look. Link to comment Share on other sites More sharing options...
Martyn Houghton Posted March 24, 2020 Author Share Posted March 24, 2020 @James Ainsworth The PM case was logged from our Hornbill Support Incident IN00157348, which we have not received an update on following the apparent closure of the linked problem last month by the development team. If you can provide details of what the 'solution' was and in the mean time we will re-try using the time recording to see if the intermittent issue is still present or has been resolved. Cheers Martyn Link to comment Share on other sites More sharing options...
James Ainsworth Posted March 25, 2020 Share Posted March 25, 2020 Hi Martyn, I'll see if I can have someone provide you with an update. 1 Link to comment Share on other sites More sharing options...
James Ainsworth Posted March 25, 2020 Share Posted March 25, 2020 Hi Martyn, I've not been able to ascertain the exact details of the solution. There was a possible root cause identified where an update would occasionally timeout. The code here was refactored in order to remove this timeout issue. As this was an intermittent issue and there wasn't any indication that we were able to replicate, it may have been difficult to guarantee that this solution would work. This had been reported by other customers. Since the update there were not any reports from the other customers of this continuing to be an issue. We would love to hear that this is the same case for you once you re-try using it again. If you do happen to have an issue, we will be sure to get another incident raised and do some further investigation. Regards, James 1 Link to comment Share on other sites More sharing options...
Martyn Houghton Posted March 26, 2020 Author Share Posted March 26, 2020 @James Ainsworth Thanks for the update. I will ask the time to proactively monitor the time recording reliability and let you know. Cheers Martyn Link to comment Share on other sites More sharing options...
Alberto M Posted April 29, 2020 Share Posted April 29, 2020 On 2/4/2020 at 5:04 PM, Martyn Houghton said: Timesheet entries are not saved when updating a request with time spent Hi. I'm having this issue as well. Any update action I add to a request where I add a time to the timesheet, adds no time. 1 Link to comment Share on other sites More sharing options...
Martin.bowman Posted June 1, 2020 Share Posted June 1, 2020 @James Ainsworth Hi James, I came across this this morning, I have made a few updates on incidents and added time but my timesheet is only displaying one entry from today. I know I definitely recorded an update with 3 minutes time against it as well as the 10 minutes that is being displayed. I also checked in database direct in case it was just a display issue but it is the same. This has also been reported by other members of my team. SELECT * FROM h_timesheet_values where h_member = 'martin.bowman' and DATE(h_time) = '2020-06-01' 1 Link to comment Share on other sites More sharing options...
James Ainsworth Posted June 1, 2020 Share Posted June 1, 2020 Hi Martin, I'll feed this back to the development team. There is an update for Timesheet Manager this isn't too far away. While I don't think that this particular issue was directly addressed, there was a significant rewrite of some of the underlying code which will improve performance and possible issues like this will have been fixed in passing. I don't believe we were able to replicate your issue internally which can make it a challenge for finding a fix. Hopefully the new Timesheet Manager update will help. I don't have a time frame yet, but possibly in the next view weeks. Regards, James 1 Link to comment Share on other sites More sharing options...
Martyn Houghton Posted June 26, 2020 Author Share Posted June 26, 2020 @James Ainsworth @AlexTumber Just to confirm this is still occurring, even after the application of the recent Timesheet Manager builds, include the latest 152. Cheers Martyn 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