Up until recently, it was a quite painful experience to edit Tempo accounts in next-gen project issues, because the field was not available on the edit issue screen.
A suboptimal (yet functional) workaround was to use the bulk edit interface and edit the issues in bulk even if only one of them needed to be edited. This was annoying, but it worked.
It would however appear the tempo accounts field has now been removed from bulk editing as well, making accounts entirely unusable for next-gen projects, or in other words, making Tempo entirely unusable for next-gen projects.
I've tried changing the features and "apps" settings for the next-gen project, to no avail. Other than setting a default Tempo account for new issues, I have found no way to change the value for existing issues.
Is there another known workaround ?
I know Tempo has been answering queries on this on other threads (one which you posted on) - but it'd be best to contact them directly via their support page for advice as an external app vendor.
Click here for their support options on the Atlassian Marketplace.
I also saw this comment on JSWCLOUD-18544 from December 2019 which was in response to a question about Tempo Account field, that confirms a team has started working on this.
Jira is a powerful tool that helps teams to plan, manage, and report on their work. We love using Jira, especially for its ability to track issue progress. But how to monitor the...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events