How to detect moving time?

[l.mgebrishvili]

Hello everyone, I have the following question: when an issue is created in Project A, and then moved to the Project B. How can i detect the time of moving? Thanks 

[l.mgebrishvili]

May be this is the problem, request type is not identified? Why does this happen? 

[Angélica Luz]

Hi l.mgebrishvili,

Welcome to Atlassian Community!

It’s possible to get this information on the ticket history.

This is how it shows on the new view:

This is how it shows on the old view:

To confirm the exact time, if it was recently moved as the examples, you need to hover the mouse over the "10 minutes ago" or "2 days ago", so it will show the date and time.

If you have any other question, please let us know.

Regards,
Angélica

[l.mgebrishvili]

[l.mgebrishvili]

I moved the issue from one project to another . Previously created the additional status "move to squad" .On the screen you may see the second project in which the time of " move to squad " is errorred. Why does this happen ?

thank you

[Angélica Luz]

Just for us to better understand and help you with this issue, can you please share with us a screenshot of the SLA configuration for “Time to Squad”?

[l.mgebrishvili]

Hello, I am attaching the screenshot 

[Angélica Luz]

Thank you for the screenshot.

The Time to squad should start counting when the ticket is created and it should work when moving from one project to another.

Can you add on “Start” the option “Entered status: Moved from support” just to test if it will reindex and show the correct SLA?

[l.mgebrishvili]

what to you mean "Start?

[Angélica Luz]

The start would be the Start of the SLA. On the screenshot you sent there are three columns: Start, Pause and Stop. So, as a test, you can edit the SLA and add on Start the “Entered status: Moved from support”.

Regarding the Request type, when moving a ticket it will always be empty, so it’s necessary to manually change it. 

The request type is responsible for triggering the customer notifications and also to make the ticket visible on the portal for the customer, it shouldn’t cause anything on the SLA.