Count the number of closed subtasks under an issue using smart values

[Shamanth]

Hi,

I am trying to update a custom field on the parent issue based on the number of subtasks using the JIRA automation. So far, I was able to count the number of subtasks under the issue using {{issue.subtasks.size}} which is working perfectly!

I would now want to count the subtasks that are "Closed" and update the count in the parent issue. What combination of the smart field works for this?

[somethingblue]

Hi Daniel,

There are a couple things you can check on the JIRA side:

• By default JIRA will not send you email notifications about your own changes. To modify this:
  • Choose your user icon at top right of the screen, then choose Profile,
  • Click the pencil icon next to Preferences and set My Changes to "Notify me" (more detail here).
• The Resolved transition in the workflow is in conflict with the notification event.

  • Update the Post Function in the workflow to fire the Issue Resolved (System) event in the Notification Scheme.

• Check the following:
  1. The project has no Notification Scheme defined 
     • Go to the gear icon > Issues > Notification Schemes from the right sidebar

  2. The user does not have the Browse Projects permission according to the project's permission scheme (more detail here).

     • Either edit the permission scheme to change what roles have this permission or add the user to a group that puts them into an existing role with this permission.

  3. The email sent to comment on an issue also contains an image, typically in footer. The attachment of the image will change the event triggered from 'Issue Commented' to 'Issue Updated'. A workaround is to update the notification scheme to ensure 'Issue Updated' is similar to 'Issue Commented' (more detail here)
     • Considering adding a temporary test account and specify a secondary email account that you can immediately access (gmail, yahoo, hotmail, etc) to see if notifications are received/sent to the secondary account.
     • Work with your local IT contact to verify that spam filtering is not the cause

If none of those suggestions help please check with your IT team to see if there is something on the user's end or in their mail rules causing this behavior.

Cheers,

Branden