We using latest available TEMPO plugin.
In our JIRA instance there is a bunch of projects that do not need Accounts functionality, but some do need. As soon as Teampo Account custom field is added to JIRA instance, all issues in all projects have invalid worklogs, even if JIRA project was notbeen added to any account.
Is there a way to supress Invalid Worklog notification in Timesheets view for issues in projects that are not part of any account?
I am sorry that this issue was causing major problems for you. It was not clear that the design change would have as big impact as it did. We have now fixed this in Timesheets 7.8.3, where the message will only show if you explicitly configured Account Custom Field to be required. The message will also only show up on projects that are associated with accounts. If you have any further issues that we did not fix in this change, let us know.
we are working on improvements for Accounts and this is own of the issues we are taking a look at.
So far, if you have added "Tempo Accounts" as an JIRA custom field, all issues require a value in this field. If no value is given (as happens if the Project is not connected to an Account), all the worklogs on these issues are invalid. Please note, that this is only a warning and you can simply ignore it.
If you want to avoid getting this warning, you can create a dummy account and connect all Projects to it that do not need an account. You will need to bulk edit all issues belonging to these Projects to show this dummy account.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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!
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