nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Is it possible to revert back to Jira Cloud situation of yesterday/two days before?

Lisette Berghuis

Hi,

we are preparing our migration from Jira Server to Jira Cloud and yesterday I accidentially added Tempo timesheets to our production environment instead of our sandbox. This is not how we planned it and it causes some issues.

I am pretty sure the answer is no, but well, you'll never know ☺:

I was wondering if we can 'turn back time' and do something to be again in the same situation as Wednesday evening: Jira Cloud without the Tempo Timesheet app (deleting this app and installing it again doesn't work)?
I am also in touch with Tempo, but maybe there are also some good ideas in this community.

Thanks for your feedback!

Kind regards,
Lisette

Accepted answers

Alex Koxaras -Relational-

Hi @Lisette Berghuis

Turn back time it's not (yet) possible. I've only seen it once, on Superman when he flew in the opposite direction of the spinning of the earth to save Lois

Joke's aside, no it's not possible. But it would be great if you could share what is the problem you are facing now that tempo is installed on the production environment.

The only thing you could do in such cases, is to get a backup of your cloud instance, vanilla, prior of doing anything to it. A plain brand new cloud instance. This will be handy if you need to reset things back to the way it was.

All comments

Alex Koxaras -Relational-

Hi @Lisette Berghuis

Turn back time it's not (yet) possible. I've only seen it once, on Superman when he flew in the opposite direction of the spinning of the earth to save Lois

Joke's aside, no it's not possible. But it would be great if you could share what is the problem you are facing now that tempo is installed on the production environment.

Lisette Berghuis

Hi Alex,

ohh that is a bit a pity as i saw jira as a system equivalent of superman ;-).

Thanks for your reply!

The thing is that first Jira (including Tempo) data needs to be migrated to the cloud, then you can add the Tempo timesheets app and then your timesheets will be filled with the (tempo) data that was already available in the cloud instance. When you first install Tempo Timesheets and thereafter migrate your Jira (/Tempo) data, the timesheets won't be filled anymore and stay empty.

Alex Koxaras -Relational-

@Lisette Berghuis when using the JCMA it tells you to assess your apps. After done assessing your app, you'll navigate (at one point) to the cloud site, so that you can install the apps first, and then run the migration. On my migrations, to be honest, I didn't have the case of migration timesheets as well. But I'm a bit surprised that someone told you that you first migrate the data, and then you install tempo. Sorry, for asking, but are you really certain of this?

If you are using JCMA for the migration the instructions can be found here https://help.tempo.io/cloud/en/tempo-server-migration-guide/server-to-cloud-migration-using-jcma/jira-cloud-migration-assistant-application.html

Lisette Berghuis

Thanks Alex, the process is completely clear to us now.

We interpreted the instructions incorrectly. Now it is very clear to us

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-software-cloud