Linked issue status validator not working as expected.

[sai srinivas salver]

Hello all, I created a validator using JMWE to restrict users from moving a Feature ticket to "released" while it's child tickets (Epics) are still in to-do/in progress statuses. The validator works when the user is trying to move a Feature ticket to Released status while the Epics are still in progress, it restricts them to do so. However, when the Epics are moved to Done status, I am unable to move the Feature ticket to a released status and the error message is the same as when the epics are in progress. Any suggestions on what I am doing wrong, please?

Please see the screenshot below.

[Teja(Appfire)]

Hi  ,

I am Teja from Appfire JMWE Support! Thank you for sharing your scenario.

Based on your description, it appears that you are utilizing a Linked Issues Status Validator in JMWE to restrict the transition of a Feature ticket to “Released” while its child Epics remain in either “To Do” or “In Progress” statuses. However, you are encountering an issue where the validation still prevents the transition even when all child Epics are in the “Done” status.

The Linked Issues Status Validator functions as intended in numerous scenarios; however, when addressing parent/child relationships (e.g., Feature → Epics), particularly within Advanced Roadmaps (formerly Portfolio) hierarchies, certain limitations arise. This is due to the fact that the Advanced Roadmaps hierarchy is not yet fully supported in Jira expressions. Atlassian has an open improvement request (ACJIRA-1766) to enable this hierarchy for Jira expressions.

Upon further investigation, it appears that Jira Expressions have recently introduced support for accessing parent and child issues from the Advanced Roadmaps hierarchy. Therefore, it remains unclear why the aforementioned improvement request is still pending with Atlassian, as it may not yet be fully implemented.

Workaround

If your use case is based on issue links (e.g., “is Child of”), you may consider employing the Build-your-own Condition (JMWE) https://appfire.atlassian.net/wiki/spaces/JMWEC/pages/465474365/Build-your-own+scripted+Condition to manually validate the child issues. I recommend replacing your current validator with the following:

Jira Expression:

issue.childIssues.every(it => ["Done"].includes(it.status.name))

This expression verifies that all child issues linked to the Feature (in this instance, Epics) have a status of “Done.” If any child issue is not in the “Done” status, the transition will be blocked.

Please attempt this workaround and inform us if it resolves your issue. If you require further assistance or encounter additional challenges, do not hesitate to reach out.

Best regards,
Teja

[Muhammad Kunza Haruna]

I Agree 💯 

[Ahmed Arslan]

Is your Feature issue type defined as initiative as you mentioned Epic is a child issue of Feature?

[sai srinivas salver]

Parent issue type = Feature

Child = Epic