Jira Automation: How to start and close Epic automatically depending on contained issue transitions?

[Ingo Mohr]

Hi all,

I would like to start and close my Epics automatically by working on the epics's issues alone.

i.e.

* when I start the first of its issues, the Epic should be transitioned to a certain status in its workflow

* when I close the last of its issues, the Epic should be closed, too.

How can I do this w/ Jira automation?

[Viðar Svansson [Tempo] · Accepted solution]

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

[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.

[Susanne Götz [Tempo]]

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 Kalyta]

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.