Issue Summary

The Automation rule does not display the count of rule components. There are few "hidden" components that are available in the JSON export and one particular type (jira.condition.container.block) actually counts towards the service limit. This creates a problem when you are still expecting the count has not hit the limit.

Especially, if the rule includes the If..else component (jira.condition.container.block).

More details and context on the following article:

• Automation rule message: You've reached the maximum number of 65 components allowed per rule

Steps to Reproduce

1. Create a new rule
2. Add components with if..else conditions (say ~58 of them)
3. The Rule won't allow you to add any more component irrespective of the count from the UI search suggest that the total count is less than the service limit of 65.

Expected Behaviour

Users should be able to clearly see the number of components currently used in their rules and possibly restricted from creating a new component once limit is reached.

Actual Results

• Adding any new component will result in the below error even though visually you seem to have less than 65 components
  
• Here is an additional understand if your rule is impacted due to this problem
  • Download the JSON file for the rule
  • Look for the count of - "jira.condition.container.block" element. This is the additional component being taken into consideration by the validation logic towards the count of components.

Workaround

None as this is a usability bug. However, if you are hitting the service limit then you may need to split the rule.