Estimate time not shown in standard screen scheme anymore

[EDV CIM]

Dear Community

maybe one of you could help us out because even the support of atlassians find a solution for our problem.

At the moment we have the issue at all of our project the estimated time is not showing on the screen sheme. Time Tracking ist activated and the estimated time field is added to every screen as well. I have tried to delete the screens and add them again and made reindexing everytime i made changes. We don´t have made any update on any apps or jira itself. The problem just came over night because we have use it for month.

Any suggestions?

[Tinker Fadoua · Accepted solution]

@EDV CIM 

What about the permissions on the project? IS time tracking available for a specific group? Admins only? any logged in user?

Please check project permission.

Best,

Fadoua

[EDV CIM]

@Tinker Fadoua 

Every logged user has the permission for time tracking. I have checked it after your reply ;-)

[EDV CIM]

@Tinker Fadoua 

We are using tempo since january this year and this problem first showing up on the 30 of march. As i`m the only jira administrator for our company no one could make changes and i did no changes this date for sure.

[Tinker Fadoua]

If you installed Tempo in January, then the problem with time tracking started around end of March my guessing is that Tempo is not the problem

I am looking for what could be the problem.

Best,

Fadoua

[Tinker Fadoua]

Do you recall any change made recently in Jira @EDV CIM ? You did mention that you didn't add an App but any other change that you may think it was minor that could have triggered this behaviour?

Do you have a test instance with a recent data refresh from Production?

Best,

Fadoua

[EDV CIM]

@Tinker Fadoua 

I have made a request at atlassians and the agent told me that one of our third party plugins could force the error but this is a our main productive system so any changes could only made at night. 

At this time the only change i made was editing workweek schemes for employees via the rest api because of new work contracts but i have made this a several time before march without any problems.

[Tinker Fadoua]

@EDV CIM 

Do you have a test instance? is it always very helpful to run some troubleshooting in a test instance.

You can mimic your production instance so that we can run the tests anytime.

Please let me know how it goes when you try any suggested steps.

Best,

Fadoua 

[EDV CIM]

@Tinker Fadoua 

Yes we do have a test instance but it has newer versions of jira core, software and service desk on it. The first screenshot in post is from that test instance as well.

Like i answered two posts before the only changes i made was to change the working hours/days within rest api for a few employees because of contract changes.

Sincerly

[Tinker Fadoua]

@EDV CIM it is a bummer because that would have helped to run some testing to make sure what's the problem behind your issue before you can try the fix in Production.

All the best,

Fadoua

[EDV CIM]

You are right - that`s something i found out myself the hard way sometime. We test every update within our test instance before but on this case i could not find any error after updating the test instance.

[EDV CIM]

I just check the test instance and found an older snapshot of this VM so i could get back to an older core version.

[Tinker Fadoua]

If you can install the same version than Production on a test serve @EDV CIM , it is always helpful.

[EDV CIM]

Hello @Tinker Fadoua ,

after your information i have made a rollback on the test instance so we have the same core version on test and productive system. 

What can i do next? Do you have any idea where i had to take a look first?

Greetings

[Tinker Fadoua]

Can you do a backup/restore from Production?

[EDV CIM]

I could do a backup but restoring to a older snapshot is impossible because of changes where made this time.

[Tinker Fadoua]

@EDV CIM did you check the board configuration to make sure that the Time Estimate is selected?

Just to double check.

[EDV CIM]

@Tinker Fadoua 

Hello Fedoua i found out the problem after updating the productiv system and test system. I had checked every installed add on and find out that there is one add on which was installed on productive but not in test. After installing it on the test system we had the same error. 

I just opend a ticket at the plug ins support.

Thanks for your help.

[Tinker Fadoua]

I am really glad you were able to find the issue @EDV CIM ! Which plugin was behind your miseries?

[EDV CIM]

@Tinker Fadoua 

The PlugIn is called "UnView" by Accxia and it is a plug in we need to have because of General Data Protection Regulation