Tickets showing as assigned to Owner when they are not

[Mike Hillman]

We've just started noticing an issue on all tickets where when the ticket is opened they are showing as being assigned to the analyst who opens the ticket, even though the ticket isn't actually assigned to anyone and has no owner

Has anyone else noticed this issue?

[nasimg]

Yes I saw this but assumed it was a glitch - maybe related to the Supporting Teams issue (Services show all team now).

[Mike Hillman]

3 minutes ago, nasimg said:

Yes I saw this but assumed it was a glitch - maybe related to the Supporting Teams issue (Services show all team now).

Yes just spotted the Supporting Teams issue - I'm guessing they're related

 

[Victor]

We are investigating the issue. We have no indication at this point that the "supporting teams" issue and this one are related.

[AndyHill]

Our analysts can not assign calls to themselves as the Window prepopulates their name with the assign button greyed out. If they remove and readd their own name it remains greyed out. They can assign to other analysts without issue. 

[Josh Bridgens]

Can also confirm this is affecting us.

[JoanneG]

Good Morning, we are also having the same issue...

[AlexOnTheHill]

We are also experiencing the exact same issue.

Our temporary workaround has been to assign to someone else then reassign back to yourself however that seems to only work within the same team.

I have tried this with assigning to a different team and get "cannot assign to same team/analyst"

[Victor]

All instances will be affected by this issue. As mentioned in the message posted on top of this thread, the issue is being looked into. Will come back with more information as soon as I have any.

[Salman]

Good morning,

We're seeing the same issue as well.

[Mark (ESC)]

We are having the same issue, agent who creates the ticket, assigns it to another team, but they stay assigned to the ticket themselves.  

Ticket is assigned to an agent not in that Team, and that agent is the agent who initially created the ticket as pushed to another team.

Because of this ticket seems locked to others in that assigned Team and they cannot assign to themselves.  Hope that makes sense.

Seems only admin users can assign the ticket correctly. 

[John C]

Can also confirm this is affecting us.

 

[HGrigsby]

We are affected too

 

[Deen]

All, we have pushed out a fix for this, it would be worth flushing your browser cache then checking to see if this remains a problem.

[Mike Hillman]

1 minute ago, Deen said:

All, we have pushed out a fix for this, it would be worth flushing your browser cache then checking to see if this remains a problem.

Thanks - We'd just noticed that everything seemed to be working correctly again, we're just testing

 

[AlexOnTheHill]

After a force refresh I am still seeing this issue, testing continues with colleagues

[Mike Hillman]

1 minute ago, Mike Hillman said:

Thanks - We'd just noticed that everything seemed to be working correctly again, we're just testing

 

Yep, all looking good  

[AlexOnTheHill]

7 minutes ago, AlexOnTheHill said:

After a force refresh I am still seeing this issue, testing continues with colleagues

After assigning to a different team I was then able to assign to myself/colleagues/another team.

Colleagues are now reporting things appear to be ok.

[Sam P]

Affecting us despite refresh

[Alberto M]

Yes. Creating a mess around here.

 

[Deen]

@Sam P Have you completely flushed your browser cache? you should not be seeing the problem after that.

[Adrian Simpkins]

Still seeing this issue on our instance - i have had several staff clear the cache in browser and reload but still seeing the same issue

Thanks

[Sam P]

@Deen yes full flush still an issue

 

[John C]

still an isssue

[Smurfy]

This is affecting us too