|
Post by account_disabled on Mar 14, 2024 21:16:40 GMT 12
If users reached it to report a problem it means that this bug really hurts and it needs to be dealt with as soon as possible. So users highlighted a lot of problem areas Old cases are not saved. I want to see what they did and how screenshots logs recommendations. Situations sometimes repeat themselves but the case is no longer on the portal. When Jira responds to a case by mail the status does not change it hangs in the status of waiting for the client. Are as if they are waiting for action but in fact the case is being worked on by an Buy Email List engineer. There are loading restrictions. When downlo ading large logs the engineer separately sends a link for downloading. It would be good if it was within the framework of the application something can be thrown into the application itself and the large file can be uploaded via a link in the application to a cloud drive bypassing the engineer. Gradually and taking into account feedback they began to transfer to a new portal and other projects. Change links in letters to authors and participants of requests. Using them the first thing we did was introduce users to the new portal. And the next step was to put a banner on the old Jira portal that soon there will be nothing here were moving. Clients tried to use the old portal until the last minute force of habit. There were situations when they came to the service manager and asked to do it as it was because it was unusual. We didnt wait for everyone to get used to it we closed our old portal.
|
|