Renamed project key, Tempo internal issue no longer working

Hi

I had an internal Tempo issue called "Meetings" which was used for logging any meeting hours against. Its key was previously ABD-11.

I renamed the project's Key from ABD to ITS, and the issue got renamed ITS-11. It even shows up in the list of internal issues in the Tempo Administration screen. All looking good so far.

However it seems to have lost the internal issue 'behaviour', namely that I shouldn't have to enter a remaining estimate, when I log time against it. Also, I can't delete it from the list either.

Has anyone else had any experience of this (and ideally, know what the fix is?)

Thanks

2 answers

I've just managed to remove it by moving it to the bottom of the list and then trying again. It deleted it once it was at the bottom of the list.

Then (still on the same screen), I added it back in as an internal issue, and the behavior is back to normal.

Hi Richard,

 

Glad to hear you managed to get the behaviour back to normal.

The behaviour you were experiencing is a confirmed bug in the current version of Tempo Timesheets.

 

Best regards,
Sigrún
Tempo 



Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Oct 09, 2018 in Jira Core

How to manage many similar workflows?

I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...

402 views 6 0
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you