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; } } }

How to disable invalid worklog for issues without accounts

Maksym Kalyta1

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?

Accepted answers

Viðar Svansson

Hello Maksym,

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.

Best,
Viðar

All comments

Susanne Götz [T1

Hi Maksym,

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.

Kind regards,

Susanne

Maksym Kalyta1

Well.... For our number of projects and issues it will be an overkill to assign dummy account. I think we would wait with TEMPO purchase until this issue will be resolved.

Viðar Svansson

Hello Maksym,

Best,
Viðar

Darin Klein

After upgrading JIRA to 6.2.4 and with the Tempo Timesheets plugin version 7.9 we are again seeing the "invalid worklog" message even though we don't have "account" as required.

Welcome!

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

Quick Links

Find more posts tagged with

jira

jira-administration

tempo