LosOjos (23rd June 2010)
Yours truly has strongly supported this request!
Some colleagues at Capita agree that the CR section needs rationalising.
They have to sort out the many different CRs on the same theme in readiness for the Software Consultation meetings each year!
Last edited by Sivadam; 23rd June 2010 at 11:07 AM.
Plus, what does published for consultation mean?
Why aren't a handful selected each week and publicised. I'd like to vote on something that i may use in the future, as with your change request. I wont necessarily go searching for it.
We shouldn't have to wait until we find something wrong or we need it, to then go hunting to see if anyone else needs the same.
There should be some proactive marketing of what we want, not use begging for things to be changed.
As far as reforming the CR system goes, I'd suggest that someone from Capita checks CRs and flags them as - Already Implemented or - Planned for XYZ release, as there a quite a few in there that have been implemented already.
Maybe that would help, as would an overall list of the most and least popular CRs, across all modules, in order to see what's most/least likely to get done...
All the most popular CRs are analysed for discussions at the Software Consultation meetings each year!
Whilst we're on this subject of revamping change requests (which I do agree with).
I really think that the whole of SupportNet should be revamped - I mean, come on, the site looks like something I created using Angelfire (if you remember that, you'll know how "lol" it was) back in 1999...
The thing which annoys me most is the amount of errors I receive on an almost daily basis, I can't vote for that change request today as "the application encountered an error". This also happens frequently when trying to log and view existing cases and no matter what you do (use a different browser, log in/out, clear cookies) it does not resolve itself.
Change requests need to be categorised in a better and clearer way and maybe have some indication to us (customers) if they are being worked on or not.
Solution auditing... a lot of the solutions published are poorly written and often don't really make any sense. Old solutions are generally not updated either.
Still whilst these are all great ideas, I seriously doubt that they will ever come to fruition as they simply don't make any money.
Capita SupportNet online survey
We can only hope that they take heed of our feedback, and maybe even give us the results so we know what's going on.
The vote is taken from all the CRs not yet implemented. A shotlist is drawn up and voted on further until a list is drawn up in order of 'votes for' theis list is taken back to Capita where the software people work with the list to create their own list of priorities a possibilities in time scale available.
At least this was the case with those i have been to. Local Autority representatives attend the meetings as they 'should' have an overview of what is most needed an viable.
The Software Consultation Meetings are run by the Capita Product Managers. They are usually advertised on SupportNet and Users can volunteer to attend!
See Resource 16890 on SupportNet. Unfortunately I could not attend this one but I was invited to submit my ideas re. the CRs which I have subsequently done!
Last edited by Sivadam; 23rd June 2010 at 06:28 PM.
Can you roll effect date forward to when they start, then bulk update the details. The MoT shouldn't get picked up anyway, so where is the problem??
What do you mean false-positive?
There are currently 1 users browsing this thread. (0 members and 1 guests)