Issue Summary

Removing a Product like JWM from the Atlassian Cloud site does not reflect on the Automation for JIRA Cloud Usage page immediately.

Steps to Reproduce

1. Have a JIRA Software License and JIRA Work Management License on the Atlassian Cloud Site.
2. Create some Business Projects and enter some data into those projects.
3. Create some basic automation rules that make some Issue Editing Actions on these Business Projects.
4. Running these automation rules will utilise the executions from JWM license.
5. Remove the JWM license from the Site. Go to "Jira Settings" > "Billing". You need to be a "Site Admin" or "Billing Contact" to access this page.
6. The Product will go into the "Deactivated" state and show the below message you review the product on the "Billing" page
   
7. The Business Project should be intact as we have "JIRA Software" Paid License still intact.
8. After "Updating the Automation Rule Homes", the rules should be counted towards the "JIRA Software" executions. However, we still see the deactivated product in the Automation Usage tab. (Screenshot below), and the Business project Automation rules are still counted towards the deactivated Product.
   
9. This will "Abort" automation rules due to the error "Automation Rule Execution Limit breached".

Expected Results

• As soon as the "Jira Work Management" License is Removed from the site, the automation usage tab needs to remove the executions for it for any Automation rules being targeted towards JWM projects/Business Projects.
• Then we can use the "Updating the Automation Rule Homes" option to point the rules to consume from the "Jira Software" product.

Actual Results

• After removing the "Jira Work Management" License, Automation rules in the Business Project still consume the Jira Work Management Execution. Sometimes which can result in consuming all the rule executions and resulting in automation rules being "Aborted".
• In this case "Updating the Automation Rule Homes" option also doesn't work as Product License is still detectable in the Application.

Workaround

• No Workaround as of now.
• Upgrading the Product is not an option here because users are trying to Deactivate the Product.
• Please reach out to Atlassian Support for help.