Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Cannot transfer one organisation to another

Gero
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
September 9, 2021

Hello, I did some mess while setting up my Jira products, and have now 3 different organisations. Would like to get rid of two of them, but as far as I've understood it's incredibly impossible. So I tried transferring both to the only one I'd like to keep, but I keep receiving an error message saying like

The action cannot be performed at this time. Try later.

 Somebody can help me about that? I'm administrator of every organisation, and the only one with a verified domain is the target one.

Here attached an image of what I get; it's in Italian, but you can see the error message at the end.

 

image.png

1 answer

1 accepted

0 votes
Answer accepted
Rahul Aich [Nagra]
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
March 18, 2014

I got this response from Tempo support team

" I was checking with the dev team, and I think we found the problem.
When you log time through Tempo without start time, the worklogs automatically get the timestamp "midnight". The burndown in JIRA Agile shows the time logged until "now", so hours logged in Tempo will not show up until after midnight.
To avoid this, you can check the "Log work with start time" in the Tempo Global Configuration (Administration-> Add-ons, Tempo Global Configuration, in the Time Tracking Permissions and Validation section). When using this, all worklogs should show up in the burndown as soon as you log them."

Suggest an answer

Log in or Sign up to answer