Solved by Status Rollup synchronizer in version 1.2.

As synchronizers may be confusing, it might require some time to dig. The documentation is out there (see the release notes), introductory videos are coming.

Thank you all for voting and feedback!

Current idea is to achieve this through a synchronizer, which can be set up on a specific structure with the following parameters:

- workflow actions to execute to make issue resolved (first applicable will be executed)
- workflow actions to execute to make issue non-resolved (ditto)

We can also add parameters "parent issue types" and "parent projects", and if parent issue is not from those types/projects, it won't be affected.

But configurable... e.g. in some projects we want this, in others we don't want this. (or per parent issuetype? -- or would this be too confusing)

I'm sorry, the description of this idea is too confusing - it's actually implementation thoughts back from the inception of the project. I'll have it edited.

However, the idea itself remains. Implementing it with JIRA is a bit of a challenge, so that's why the idea is "under review" until some later release where we get closer to JIRA workflow integration.

Igor

Hi Igor,

What do you meant by H4J-provided events?

How to achieve this in JIRA?

Thanks