|
54246
|
Platform Sprint 4 Q2 - Platform Team - Scrum Board Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Usage | Windsurf
Usage | Windsurf
Allow owner's role to be selected when setting up a trial by LakyLak · Pull Request #12092 · jiminny/app
Allow owner's role to be selected when setting up a trial by LakyLak · Pull Request #12092 · jiminny/app
Pipelines - jiminny/app
Pipelines - jiminny/app
[SRD-6848] Sidekick SMS issue - Jira
[SRD-6848] Sidekick SMS issue - Jira
CloudWatch | us-east-2
CloudWatch | us-east-2
CloudWatch | us-east-2
CloudWatch | us-east-2
Jiminny
Jiminny
Jiminny\Exceptions\SocialAccountTokenInvalidException: Your Salesforce account has become disconnected. Please login to Jiminny to reconnect. — jiminny — app
Jiminny\Exceptions\SocialAccountTokenInvalidException: Your Salesforce account has become disconnected. Please login to Jiminny to reconnect. — jiminny — app
Allow owner's role to be selected when setting up a trial by LakyLak · Pull Request #12092 · jiminny/app
Allow owner's role to be selected when setting up a trial by LakyLak · Pull Request #12092 · jiminny/app
[SRD-6862] ‘User does not have any of the necessary access rights’ when trying to see another team’s performance scored with the AI ACS in team insights. - Jira
[SRD-6862] ‘User does not have any of the necessary access rights’ when trying to see another team’s performance scored with the AI ACS in team insights. - Jira
New Tab
New Tab
[JY-20912] Fallback mechanism for users with active SF tokens for CRM Matching - Jira
[JY-20912] Fallback mechanism for users with active SF tokens for CRM Matching - Jira
[JY-20771] Call Scoring filter for Exec reports - Jira
[JY-20771] Call Scoring filter for Exec reports - Jira
[JY-20878] SCIM > Allow customers to manage user roles through SCIM - Jira
[JY-20878] SCIM > Allow customers to manage user roles through SCIM - Jira
[JY-20879] Enable users to use their new activity types - Jira
[JY-20879] Enable users to use their new activity types - Jira
Project Phoenix – Figma
Project Phoenix – Figma
[JY-20847] Users can filter Scores in Team Insights by Host - Jira
[JY-20847] Users can filter Scores in Team Insights by Host - Jira
[JY-20534] AI Call Scoring quick access in Playback header - Jira
[JY-20534] AI Call Scoring quick access in Playback header - Jira
Close tab
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Sidebar
Sidebar
Top Bar
Top Bar
Main Content
Main Content
Collapse sidebar [
Collapse sidebar [
Switch sites or apps
Switch sites or apps
Go to your Jira homepage
Search, press enter to navigate to advanced search with your text query
Create...
|
Firefox
|
[JY-20534] AI Call Scoring quick access in Playbac [JY-20534] AI Call Scoring quick access in Playback header - Jira — Work...
|
jiminny.atlassian.net/browse/JY-20534
|
54246
|
|
54247
|
Platform Sprint 4 Q2 - Platform Team - Scrum Board Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Usage | Windsurf
Usage | Windsurf
Allow owner's role to be selected when setting up a trial by LakyLak · Pull Request #12092 · jiminny/app
Allow owner's role to be selected when setting up a trial by LakyLak · Pull Request #12092 · jiminny/app
Pipelines - jiminny/app
Pipelines - jiminny/app
[SRD-6848] Sidekick SMS issue - Jira
[SRD-6848] Sidekick SMS issue - Jira
CloudWatch | us-east-2
CloudWatch | us-east-2
CloudWatch | us-east-2
CloudWatch | us-east-2
Jiminny
Jiminny
Jiminny\Exceptions\SocialAccountTokenInvalidException: Your Salesforce account has become disconnected. Please login to Jiminny to reconnect. — jiminny — app
Jiminny\Exceptions\SocialAccountTokenInvalidException: Your Salesforce account has become disconnected. Please login to Jiminny to reconnect. — jiminny — app
Allow owner's role to be selected when setting up a trial by LakyLak · Pull Request #12092 · jiminny/app
Allow owner's role to be selected when setting up a trial by LakyLak · Pull Request #12092 · jiminny/app
[SRD-6862] ‘User does not have any of the necessary access rights’ when trying to see another team’s performance scored with the AI ACS in team insights. - Jira
[SRD-6862] ‘User does not have any of the necessary access rights’ when trying to see another team’s performance scored with the AI ACS in team insights. - Jira
New Tab
New Tab
[JY-20912] Fallback mechanism for users with active SF tokens for CRM Matching - Jira
[JY-20912] Fallback mechanism for users with active SF tokens for CRM Matching - Jira
[JY-20771] Call Scoring filter for Exec reports - Jira
[JY-20771] Call Scoring filter for Exec reports - Jira
[JY-20878] SCIM > Allow customers to manage user roles through SCIM - Jira
[JY-20878] SCIM > Allow customers to manage user roles through SCIM - Jira
[JY-20879] Enable users to use their new activity types - Jira
[JY-20879] Enable users to use their new activity types - Jira
Project Phoenix – Figma
Project Phoenix – Figma
[JY-20847] Users can filter Scores in Team Insights by Host - Jira
[JY-20847] Users can filter Scores in Team Insights by Host - Jira
[JY-20534] AI Call Scoring quick access in Playback header - Jira
[JY-20534] AI Call Scoring quick access in Playback header - Jira
Close tab
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)...
|
Firefox
|
[JY-20534] AI Call Scoring quick access in Playbac [JY-20534] AI Call Scoring quick access in Playback header - Jira — Work...
|
jiminny.atlassian.net/browse/JY-20534
|
54247
|
|
54248
|
Platform Sprint 4 Q2 - Platform Team - Scrum Board Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Usage | Windsurf
Usage | Windsurf
Allow owner's role to be selected when setting up a trial by LakyLak · Pull Request #12092 · jiminny/app
Allow owner's role to be selected when setting up a trial by LakyLak · Pull Request #12092 · jiminny/app
Pipelines - jiminny/app
Pipelines - jiminny/app
[SRD-6848] Sidekick SMS issue - Jira
[SRD-6848] Sidekick SMS issue - Jira
CloudWatch | us-east-2
CloudWatch | us-east-2
CloudWatch | us-east-2
CloudWatch | us-east-2
Jiminny
Jiminny
Jiminny\Exceptions\SocialAccountTokenInvalidException: Your Salesforce account has become disconnected. Please login to Jiminny to reconnect. — jiminny — app
Jiminny\Exceptions\SocialAccountTokenInvalidException: Your Salesforce account has become disconnected. Please login to Jiminny to reconnect. — jiminny — app
Allow owner's role to be selected when setting up a trial by LakyLak · Pull Request #12092 · jiminny/app
Allow owner's role to be selected when setting up a trial by LakyLak · Pull Request #12092 · jiminny/app
[SRD-6862] ‘User does not have any of the necessary access rights’ when trying to see another team’s performance scored with the AI ACS in team insights. - Jira
[SRD-6862] ‘User does not have any of the necessary access rights’ when trying to see another team’s performance scored with the AI ACS in team insights. - Jira
New Tab
New Tab
[JY-20912] Fallback mechanism for users with active SF tokens for CRM Matching - Jira
[JY-20912] Fallback mechanism for users with active SF tokens for CRM Matching - Jira
[JY-20771] Call Scoring filter for Exec reports - Jira
[JY-20771] Call Scoring filter for Exec reports - Jira
[JY-20878] SCIM > Allow customers to manage user roles through SCIM - Jira
[JY-20878] SCIM > Allow customers to manage user roles through SCIM - Jira
[JY-20879] Enable users to use their new activity types - Jira
[JY-20879] Enable users to use their new activity types - Jira
Project Phoenix – Figma
Project Phoenix – Figma
[JY-20847] Users can filter Scores in Team Insights by Host - Jira
[JY-20847] Users can filter Scores in Team Insights by Host - Jira
[JY-20534] AI Call Scoring quick access in Playback header - Jira
[JY-20534] AI Call Scoring quick access in Playback header - Jira
Close tab
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Sidebar
Sidebar
Top Bar
Top Bar
Main Content
Main Content
Collapse sidebar [
Collapse sidebar [
Switch sites or apps
Switch sites or apps
Go to your Jira homepage
Search, press enter to navigate to advanced search with your text query
Create
Create...
|
Firefox
|
[JY-20534] AI Call Scoring quick access in Playbac [JY-20534] AI Call Scoring quick access in Playback header - Jira — Work...
|
jiminny.atlassian.net/browse/JY-20534
|
54248
|
|
54249
|
Platform Sprint 4 Q2 - Platform Team - Scrum Board Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Usage | Windsurf
Usage | Windsurf
Allow owner's role to be selected when setting up a trial by LakyLak · Pull Request #12092 · jiminny/app
Allow owner's role to be selected when setting up a trial by LakyLak · Pull Request #12092 · jiminny/app
Pipelines - jiminny/app
Pipelines - jiminny/app
[SRD-6848] Sidekick SMS issue - Jira
[SRD-6848] Sidekick SMS issue - Jira
CloudWatch | us-east-2
CloudWatch | us-east-2
CloudWatch | us-east-2
CloudWatch | us-east-2
Jiminny
Jiminny
Jiminny\Exceptions\SocialAccountTokenInvalidException: Your Salesforce account has become disconnected. Please login to Jiminny to reconnect. — jiminny — app
Jiminny\Exceptions\SocialAccountTokenInvalidException: Your Salesforce account has become disconnected. Please login to Jiminny to reconnect. — jiminny — app
Allow owner's role to be selected when setting up a trial by LakyLak · Pull Request #12092 · jiminny/app
Allow owner's role to be selected when setting up a trial by LakyLak · Pull Request #12092 · jiminny/app
[SRD-6862] ‘User does not have any of the necessary access rights’ when trying to see another team’s performance scored with the AI ACS in team insights. - Jira
[SRD-6862] ‘User does not have any of the necessary access rights’ when trying to see another team’s performance scored with the AI ACS in team insights. - Jira
New Tab
New Tab
[JY-20912] Fallback mechanism for users with active SF tokens for CRM Matching - Jira
[JY-20912] Fallback mechanism for users with active SF tokens for CRM Matching - Jira
[JY-20771] Call Scoring filter for Exec reports - Jira
[JY-20771] Call Scoring filter for Exec reports - Jira
[JY-20878] SCIM > Allow customers to manage user roles through SCIM - Jira
[JY-20878] SCIM > Allow customers to manage user roles through SCIM - Jira
[JY-20879] Enable users to use their new activity types - Jira
[JY-20879] Enable users to use their new activity types - Jira
Project Phoenix – Figma
Project Phoenix – Figma
[JY-20847] Users can filter Scores in Team Insights by Host - Jira
[JY-20847] Users can filter Scores in Team Insights by Host - Jira
[JY-20534] AI Call Scoring quick access in Playback header - Jira
[JY-20534] AI Call Scoring quick access in Playback header - Jira
Close tab
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Sidebar
Sidebar
Top Bar
Top Bar
Main Content
Main Content
Collapse sidebar [
Collapse sidebar [
Switch sites or apps
Switch sites or apps
Go to your Jira homepage
Search, press enter to navigate to advanced search with your text query
Create
Create
Rovo Ask Rovo
Ask Rovo
Notifications
Notifications
Help
Help
Settings
Settings...
|
Firefox
|
[JY-20534] AI Call Scoring quick access in Playbac [JY-20534] AI Call Scoring quick access in Playback header - Jira — Work...
|
jiminny.atlassian.net/browse/JY-20534
|
54249
|
|
54250
|
Platform Sprint 4 Q2 - Platform Team - Scrum Board Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Usage | Windsurf
Usage | Windsurf
Allow owner's role to be selected when setting up a trial by LakyLak · Pull Request #12092 · jiminny/app
Allow owner's role to be selected when setting up a trial by LakyLak · Pull Request #12092 · jiminny/app
Pipelines - jiminny/app
Pipelines - jiminny/app
[SRD-6848] Sidekick SMS issue - Jira
[SRD-6848] Sidekick SMS issue - Jira
CloudWatch | us-east-2
CloudWatch | us-east-2
CloudWatch | us-east-2
CloudWatch | us-east-2
Jiminny
Jiminny
Jiminny\Exceptions\SocialAccountTokenInvalidException: Your Salesforce account has become disconnected. Please login to Jiminny to reconnect. — jiminny — app
Jiminny\Exceptions\SocialAccountTokenInvalidException: Your Salesforce account has become disconnected. Please login to Jiminny to reconnect. — jiminny — app
Allow owner's role to be selected when setting up a trial by LakyLak · Pull Request #12092 · jiminny/app
Allow owner's role to be selected when setting up a trial by LakyLak · Pull Request #12092 · jiminny/app
[SRD-6862] ‘User does not have any of the necessary access rights’ when trying to see another team’s performance scored with the AI ACS in team insights. - Jira
[SRD-6862] ‘User does not have any of the necessary access rights’ when trying to see another team’s performance scored with the AI ACS in team insights. - Jira
New Tab
New Tab
[JY-20912] Fallback mechanism for users with active SF tokens for CRM Matching - Jira
[JY-20912] Fallback mechanism for users with active SF tokens for CRM Matching - Jira
[JY-20771] Call Scoring filter for Exec reports - Jira
[JY-20771] Call Scoring filter for Exec reports - Jira
[JY-20878] SCIM > Allow customers to manage user roles through SCIM - Jira
[JY-20878] SCIM > Allow customers to manage user roles through SCIM - Jira
[JY-20879] Enable users to use their new activity types - Jira
[JY-20879] Enable users to use their new activity types - Jira
Project Phoenix – Figma
Project Phoenix – Figma
[JY-20847] Users can filter Scores in Team Insights by Host - Jira
[JY-20847] Users can filter Scores in Team Insights by Host - Jira
[JY-20534] AI Call Scoring quick access in Playback header - Jira
[JY-20534] AI Call Scoring quick access in Playback header - Jira
Close tab
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)...
|
Firefox
|
[JY-20534] AI Call Scoring quick access in Playbac [JY-20534] AI Call Scoring quick access in Playback header - Jira — Work...
|
jiminny.atlassian.net/browse/JY-20534
|
54250
|
|
54251
|
Platform Sprint 4 Q2 - Platform Team - Scrum Board Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Usage | Windsurf
Usage | Windsurf
Allow owner's role to be selected when setting up a trial by LakyLak · Pull Request #12092 · jiminny/app
Allow owner's role to be selected when setting up a trial by LakyLak · Pull Request #12092 · jiminny/app
Pipelines - jiminny/app
Pipelines - jiminny/app
[SRD-6848] Sidekick SMS issue - Jira
[SRD-6848] Sidekick SMS issue - Jira
CloudWatch | us-east-2
CloudWatch | us-east-2
CloudWatch | us-east-2
CloudWatch | us-east-2
Jiminny
Jiminny
Jiminny\Exceptions\SocialAccountTokenInvalidException: Your Salesforce account has become disconnected. Please login to Jiminny to reconnect. — jiminny — app
Jiminny\Exceptions\SocialAccountTokenInvalidException: Your Salesforce account has become disconnected. Please login to Jiminny to reconnect. — jiminny — app
Allow owner's role to be selected when setting up a trial by LakyLak · Pull Request #12092 · jiminny/app
Allow owner's role to be selected when setting up a trial by LakyLak · Pull Request #12092 · jiminny/app
[SRD-6862] ‘User does not have any of the necessary access rights’ when trying to see another team’s performance scored with the AI ACS in team insights. - Jira
[SRD-6862] ‘User does not have any of the necessary access rights’ when trying to see another team’s performance scored with the AI ACS in team insights. - Jira
New Tab
New Tab
[JY-20912] Fallback mechanism for users with active SF tokens for CRM Matching - Jira
[JY-20912] Fallback mechanism for users with active SF tokens for CRM Matching - Jira
[JY-20771] Call Scoring filter for Exec reports - Jira
[JY-20771] Call Scoring filter for Exec reports - Jira
[JY-20878] SCIM > Allow customers to manage user roles through SCIM - Jira
[JY-20878] SCIM > Allow customers to manage user roles through SCIM - Jira
[JY-20879] Enable users to use their new activity types - Jira
[JY-20879] Enable users to use their new activity types - Jira
Project Phoenix – Figma
Project Phoenix – Figma
[JY-20847] Users can filter Scores in Team Insights by Host - Jira
[JY-20847] Users can filter Scores in Team Insights by Host - Jira
[JY-20534] AI Call Scoring quick access in Playback header - Jira
[JY-20534] AI Call Scoring quick access in Playback header - Jira
Close tab
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Sidebar
Sidebar
Top Bar
Top Bar
Main Content
Main Content
Collapse sidebar [
Collapse sidebar [
Switch sites or apps
Switch sites or apps
Go to your Jira homepage
Search, press enter to navigate to advanced search with your text query
Create
Create
Rovo Ask Rovo
Ask Rovo
Notifications
Notifications
Help
Help
Settings...
|
Firefox
|
[JY-20534] AI Call Scoring quick access in Playbac [JY-20534] AI Call Scoring quick access in Playback header - Jira — Work...
|
jiminny.atlassian.net/browse/JY-20534
|
54251
|
|
54252
|
Platform Sprint 4 Q2 - Platform Team - Scrum Board Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Usage | Windsurf
Usage | Windsurf
Allow owner's role to be selected when setting up a trial by LakyLak · Pull Request #12092 · jiminny/app
Allow owner's role to be selected when setting up a trial by LakyLak · Pull Request #12092 · jiminny/app
Pipelines - jiminny/app
Pipelines - jiminny/app
[SRD-6848] Sidekick SMS issue - Jira
[SRD-6848] Sidekick SMS issue - Jira
CloudWatch | us-east-2
CloudWatch | us-east-2
CloudWatch | us-east-2
CloudWatch | us-east-2
Jiminny
Jiminny
Jiminny\Exceptions\SocialAccountTokenInvalidException: Your Salesforce account has become disconnected. Please login to Jiminny to reconnect. — jiminny — app
Jiminny\Exceptions\SocialAccountTokenInvalidException: Your Salesforce account has become disconnected. Please login to Jiminny to reconnect. — jiminny — app
Allow owner's role to be selected when setting up a trial by LakyLak · Pull Request #12092 · jiminny/app
Allow owner's role to be selected when setting up a trial by LakyLak · Pull Request #12092 · jiminny/app
[SRD-6862] ‘User does not have any of the necessary access rights’ when trying to see another team’s performance scored with the AI ACS in team insights. - Jira
[SRD-6862] ‘User does not have any of the necessary access rights’ when trying to see another team’s performance scored with the AI ACS in team insights. - Jira
New Tab
New Tab
[JY-20912] Fallback mechanism for users with active SF tokens for CRM Matching - Jira
[JY-20912] Fallback mechanism for users with active SF tokens for CRM Matching - Jira
[JY-20771] Call Scoring filter for Exec reports - Jira
[JY-20771] Call Scoring filter for Exec reports - Jira
[JY-20878] SCIM > Allow customers to manage user roles through SCIM - Jira
[JY-20878] SCIM > Allow customers to manage user roles through SCIM - Jira
[JY-20879] Enable users to use their new activity types - Jira
[JY-20879] Enable users to use their new activity types - Jira
Project Phoenix – Figma
Project Phoenix – Figma
[JY-20847] Users can filter Scores in Team Insights by Host - Jira
[JY-20847] Users can filter Scores in Team Insights by Host - Jira
[JY-20534] AI Call Scoring quick access in Playback header - Jira
[JY-20534] AI Call Scoring quick access in Playback header - Jira
Close tab
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Sidebar
Sidebar
Top Bar
Top Bar
Main Content
Main Content
Collapse sidebar [
Collapse sidebar [
Switch sites or apps
Switch sites or apps
Go to your Jira homepage
Search, press enter to navigate to advanced search with your text query
Create...
|
Firefox
|
[JY-20534] AI Call Scoring quick access in Playbac [JY-20534] AI Call Scoring quick access in Playback header - Jira — Work...
|
jiminny.atlassian.net/browse/JY-20534
|
54252
|
|
54253
|
Platform Sprint 4 Q2 - Platform Team - Scrum Board Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Usage | Windsurf
Usage | Windsurf
Allow owner's role to be selected when setting up a trial by LakyLak · Pull Request #12092 · jiminny/app
Allow owner's role to be selected when setting up a trial by LakyLak · Pull Request #12092 · jiminny/app
Pipelines - jiminny/app
Pipelines - jiminny/app
[SRD-6848] Sidekick SMS issue - Jira
[SRD-6848] Sidekick SMS issue - Jira
CloudWatch | us-east-2
CloudWatch | us-east-2
CloudWatch | us-east-2
CloudWatch | us-east-2
Jiminny
Jiminny
Jiminny\Exceptions\SocialAccountTokenInvalidException: Your Salesforce account has become disconnected. Please login to Jiminny to reconnect. — jiminny — app
Jiminny\Exceptions\SocialAccountTokenInvalidException: Your Salesforce account has become disconnected. Please login to Jiminny to reconnect. — jiminny — app
Allow owner's role to be selected when setting up a trial by LakyLak · Pull Request #12092 · jiminny/app
Allow owner's role to be selected when setting up a trial by LakyLak · Pull Request #12092 · jiminny/app
[SRD-6862] ‘User does not have any of the necessary access rights’ when trying to see another team’s performance scored with the AI ACS in team insights. - Jira
[SRD-6862] ‘User does not have any of the necessary access rights’ when trying to see another team’s performance scored with the AI ACS in team insights. - Jira
New Tab
New Tab
[JY-20912] Fallback mechanism for users with active SF tokens for CRM Matching - Jira
[JY-20912] Fallback mechanism for users with active SF tokens for CRM Matching - Jira
[JY-20771] Call Scoring filter for Exec reports - Jira
[JY-20771] Call Scoring filter for Exec reports - Jira
[JY-20878] SCIM > Allow customers to manage user roles through SCIM - Jira
[JY-20878] SCIM > Allow customers to manage user roles through SCIM - Jira
[JY-20879] Enable users to use their new activity types - Jira
[JY-20879] Enable users to use their new activity types - Jira
Project Phoenix – Figma
Project Phoenix – Figma
[JY-20847] Users can filter Scores in Team Insights by Host - Jira
[JY-20847] Users can filter Scores in Team Insights by Host - Jira
[JY-20534] AI Call Scoring quick access in Playback header - Jira
[JY-20534] AI Call Scoring quick access in Playback header - Jira
Close tab
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Sidebar
Sidebar
Top Bar
Top Bar
Main Content
Main Content
Collapse sidebar [
Collapse sidebar [
Switch sites or apps
Switch sites or apps
Go to your Jira homepage
Search, press enter to navigate to advanced search with your text query
Create
Create
Rovo Ask Rovo
Ask Rovo
Notifications
Notifications
Help
Help
Settings
Settings
[EMAIL]
[EMAIL]
For you
For you
Recent
Recent
Starred
Starred
Apps
Apps...
|
Firefox
|
[JY-20534] AI Call Scoring quick access in Playbac [JY-20534] AI Call Scoring quick access in Playback header - Jira — Work...
|
jiminny.atlassian.net/browse/JY-20534
|
54253
|
|
54254
|
Platform Sprint 4 Q2 - Platform Team - Scrum Board Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Usage | Windsurf
Usage | Windsurf
Allow owner's role to be selected when setting up a trial by LakyLak · Pull Request #12092 · jiminny/app
Allow owner's role to be selected when setting up a trial by LakyLak · Pull Request #12092 · jiminny/app
Pipelines - jiminny/app
Pipelines - jiminny/app
[SRD-6848] Sidekick SMS issue - Jira
[SRD-6848] Sidekick SMS issue - Jira
CloudWatch | us-east-2
CloudWatch | us-east-2
CloudWatch | us-east-2
CloudWatch | us-east-2
Jiminny
Jiminny
Jiminny\Exceptions\SocialAccountTokenInvalidException: Your Salesforce account has become disconnected. Please login to Jiminny to reconnect. — jiminny — app
Jiminny\Exceptions\SocialAccountTokenInvalidException: Your Salesforce account has become disconnected. Please login to Jiminny to reconnect. — jiminny — app
Allow owner's role to be selected when setting up a trial by LakyLak · Pull Request #12092 · jiminny/app
Allow owner's role to be selected when setting up a trial by LakyLak · Pull Request #12092 · jiminny/app
[SRD-6862] ‘User does not have any of the necessary access rights’ when trying to see another team’s performance scored with the AI ACS in team insights. - Jira
[SRD-6862] ‘User does not have any of the necessary access rights’ when trying to see another team’s performance scored with the AI ACS in team insights. - Jira
New Tab
New Tab
[JY-20912] Fallback mechanism for users with active SF tokens for CRM Matching - Jira
[JY-20912] Fallback mechanism for users with active SF tokens for CRM Matching - Jira
[JY-20771] Call Scoring filter for Exec reports - Jira
[JY-20771] Call Scoring filter for Exec reports - Jira
[JY-20878] SCIM > Allow customers to manage user roles through SCIM - Jira
[JY-20878] SCIM > Allow customers to manage user roles through SCIM - Jira
[JY-20879] Enable users to use their new activity types - Jira
[JY-20879] Enable users to use their new activity types - Jira
Project Phoenix – Figma
Project Phoenix – Figma
[JY-20847] Users can filter Scores in Team Insights by Host - Jira
[JY-20847] Users can filter Scores in Team Insights by Host - Jira
[JY-20534] AI Call Scoring quick access in Playback header - Jira
[JY-20534] AI Call Scoring quick access in Playback header - Jira
Close tab
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Sidebar
Sidebar
Top Bar
Top Bar
Main Content
Main Content
Collapse sidebar [
Collapse sidebar [
Switch sites or apps
Switch sites or apps
Go to your Jira homepage
Search, press enter to navigate to advanced search with your text query
Create...
|
Firefox
|
[JY-20534] AI Call Scoring quick access in Playbac [JY-20534] AI Call Scoring quick access in Playback header - Jira — Work...
|
jiminny.atlassian.net/browse/JY-20534
|
54254
|
|
54255
|
Platform Sprint 4 Q2 - Platform Team - Scrum Board Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Usage | Windsurf
Usage | Windsurf
Allow owner's role to be selected when setting up a trial by LakyLak · Pull Request #12092 · jiminny/app
Allow owner's role to be selected when setting up a trial by LakyLak · Pull Request #12092 · jiminny/app
Pipelines - jiminny/app
Pipelines - jiminny/app
[SRD-6848] Sidekick SMS issue - Jira
[SRD-6848] Sidekick SMS issue - Jira
CloudWatch | us-east-2
CloudWatch | us-east-2
CloudWatch | us-east-2
CloudWatch | us-east-2
Jiminny
Jiminny
Jiminny\Exceptions\SocialAccountTokenInvalidException: Your Salesforce account has become disconnected. Please login to Jiminny to reconnect. — jiminny — app
Jiminny\Exceptions\SocialAccountTokenInvalidException: Your Salesforce account has become disconnected. Please login to Jiminny to reconnect. — jiminny — app
Allow owner's role to be selected when setting up a trial by LakyLak · Pull Request #12092 · jiminny/app
Allow owner's role to be selected when setting up a trial by LakyLak · Pull Request #12092 · jiminny/app
[SRD-6862] ‘User does not have any of the necessary access rights’ when trying to see another team’s performance scored with the AI ACS in team insights. - Jira
[SRD-6862] ‘User does not have any of the necessary access rights’ when trying to see another team’s performance scored with the AI ACS in team insights. - Jira
New Tab
New Tab
[JY-20912] Fallback mechanism for users with active SF tokens for CRM Matching - Jira
[JY-20912] Fallback mechanism for users with active SF tokens for CRM Matching - Jira
[JY-20771] Call Scoring filter for Exec reports - Jira
[JY-20771] Call Scoring filter for Exec reports - Jira
[JY-20878] SCIM > Allow customers to manage user roles through SCIM - Jira
[JY-20878] SCIM > Allow customers to manage user roles through SCIM - Jira
[JY-20879] Enable users to use their new activity types - Jira
[JY-20879] Enable users to use their new activity types - Jira
Project Phoenix – Figma
Project Phoenix – Figma
[JY-20847] Users can filter Scores in Team Insights by Host - Jira
[JY-20847] Users can filter Scores in Team Insights by Host - Jira
[JY-20534] AI Call Scoring quick access in Playback header - Jira
[JY-20534] AI Call Scoring quick access in Playback header - Jira
Close tab
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Sidebar
Sidebar
Top Bar
Top Bar
Main Content
Main Content
Collapse sidebar [...
|
Firefox
|
[JY-20534] AI Call Scoring quick access in Playbac [JY-20534] AI Call Scoring quick access in Playback header - Jira — Work...
|
jiminny.atlassian.net/browse/JY-20534
|
54255
|
|
54256
|
Platform Sprint 4 Q2 - Platform Team - Scrum Board Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Usage | Windsurf
Usage | Windsurf
Allow owner's role to be selected when setting up a trial by LakyLak · Pull Request #12092 · jiminny/app
Allow owner's role to be selected when setting up a trial by LakyLak · Pull Request #12092 · jiminny/app
Pipelines - jiminny/app
Pipelines - jiminny/app
[SRD-6848] Sidekick SMS issue - Jira
[SRD-6848] Sidekick SMS issue - Jira
CloudWatch | us-east-2
CloudWatch | us-east-2
CloudWatch | us-east-2
CloudWatch | us-east-2
Jiminny
Jiminny
Jiminny\Exceptions\SocialAccountTokenInvalidException: Your Salesforce account has become disconnected. Please login to Jiminny to reconnect. — jiminny — app
Jiminny\Exceptions\SocialAccountTokenInvalidException: Your Salesforce account has become disconnected. Please login to Jiminny to reconnect. — jiminny — app
Allow owner's role to be selected when setting up a trial by LakyLak · Pull Request #12092 · jiminny/app
Allow owner's role to be selected when setting up a trial by LakyLak · Pull Request #12092 · jiminny/app
[SRD-6862] ‘User does not have any of the necessary access rights’ when trying to see another team’s performance scored with the AI ACS in team insights. - Jira
[SRD-6862] ‘User does not have any of the necessary access rights’ when trying to see another team’s performance scored with the AI ACS in team insights. - Jira
New Tab
New Tab
[JY-20912] Fallback mechanism for users with active SF tokens for CRM Matching - Jira
[JY-20912] Fallback mechanism for users with active SF tokens for CRM Matching - Jira
[JY-20771] Call Scoring filter for Exec reports - Jira
[JY-20771] Call Scoring filter for Exec reports - Jira
[JY-20878] SCIM > Allow customers to manage user roles through SCIM - Jira
[JY-20878] SCIM > Allow customers to manage user roles through SCIM - Jira
[JY-20879] Enable users to use their new activity types - Jira
[JY-20879] Enable users to use their new activity types - Jira
Project Phoenix – Figma
Project Phoenix – Figma
[JY-20847] Users can filter Scores in Team Insights by Host - Jira
[JY-20847] Users can filter Scores in Team Insights by Host - Jira
[JY-20534] AI Call Scoring quick access in Playback header - Jira
[JY-20534] AI Call Scoring quick access in Playback header - Jira
Close tab
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Sidebar
Sidebar
Top Bar
Top Bar
Main Content
Main Content
Collapse sidebar [
Collapse sidebar [
Switch sites or apps
Switch sites or apps
Go to your Jira homepage
Search, press enter to navigate to advanced search with your text query
Create
Create
Rovo Ask Rovo...
|
Firefox
|
[JY-20534] AI Call Scoring quick access in Playbac [JY-20534] AI Call Scoring quick access in Playback header - Jira — Work...
|
jiminny.atlassian.net/browse/JY-20534
|
54256
|
|
54257
|
Platform Sprint 4 Q2 - Platform Team - Scrum Board Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Usage | Windsurf
Usage | Windsurf
Allow owner's role to be selected when setting up a trial by LakyLak · Pull Request #12092 · jiminny/app
Allow owner's role to be selected when setting up a trial by LakyLak · Pull Request #12092 · jiminny/app
Pipelines - jiminny/app
Pipelines - jiminny/app
[SRD-6848] Sidekick SMS issue - Jira
[SRD-6848] Sidekick SMS issue - Jira
CloudWatch | us-east-2
CloudWatch | us-east-2
CloudWatch | us-east-2
CloudWatch | us-east-2
Jiminny
Jiminny
Jiminny\Exceptions\SocialAccountTokenInvalidException: Your Salesforce account has become disconnected. Please login to Jiminny to reconnect. — jiminny — app
Jiminny\Exceptions\SocialAccountTokenInvalidException: Your Salesforce account has become disconnected. Please login to Jiminny to reconnect. — jiminny — app
Allow owner's role to be selected when setting up a trial by LakyLak · Pull Request #12092 · jiminny/app
Allow owner's role to be selected when setting up a trial by LakyLak · Pull Request #12092 · jiminny/app
[SRD-6862] ‘User does not have any of the necessary access rights’ when trying to see another team’s performance scored with the AI ACS in team insights. - Jira
[SRD-6862] ‘User does not have any of the necessary access rights’ when trying to see another team’s performance scored with the AI ACS in team insights. - Jira
New Tab
New Tab
[JY-20912] Fallback mechanism for users with active SF tokens for CRM Matching - Jira
[JY-20912] Fallback mechanism for users with active SF tokens for CRM Matching - Jira
[JY-20771] Call Scoring filter for Exec reports - Jira
[JY-20771] Call Scoring filter for Exec reports - Jira
[JY-20878] SCIM > Allow customers to manage user roles through SCIM - Jira
[JY-20878] SCIM > Allow customers to manage user roles through SCIM - Jira
[JY-20879] Enable users to use their new activity types - Jira
[JY-20879] Enable users to use their new activity types - Jira
Project Phoenix – Figma
Project Phoenix – Figma
[JY-20847] Users can filter Scores in Team Insights by Host - Jira
[JY-20847] Users can filter Scores in Team Insights by Host - Jira
[JY-20534] AI Call Scoring quick access in Playback header - Jira
[JY-20534] AI Call Scoring quick access in Playback header - Jira
Close tab
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Sidebar
Sidebar
Top Bar
Top Bar
Main Content
Main Content
Collapse sidebar [
Collapse sidebar [
Switch sites or apps
Switch sites or apps
Go to your Jira homepage
Search, press enter to navigate to advanced search with your text query
Create
Create
Rovo Ask Rovo
Ask Rovo
Notifications
Notifications
Help
Help
Settings
Settings
[EMAIL]
[EMAIL]...
|
Firefox
|
[JY-20534] AI Call Scoring quick access in Playbac [JY-20534] AI Call Scoring quick access in Playback header - Jira — Work...
|
jiminny.atlassian.net/browse/JY-20534
|
54257
|
|
54258
|
Platform Sprint 4 Q2 - Platform Team - Scrum Board Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Usage | Windsurf
Usage | Windsurf
Allow owner's role to be selected when setting up a trial by LakyLak · Pull Request #12092 · jiminny/app
Allow owner's role to be selected when setting up a trial by LakyLak · Pull Request #12092 · jiminny/app
Pipelines - jiminny/app
Pipelines - jiminny/app
[SRD-6848] Sidekick SMS issue - Jira
[SRD-6848] Sidekick SMS issue - Jira
CloudWatch | us-east-2
CloudWatch | us-east-2
CloudWatch | us-east-2
CloudWatch | us-east-2
Jiminny
Jiminny
Jiminny\Exceptions\SocialAccountTokenInvalidException: Your Salesforce account has become disconnected. Please login to Jiminny to reconnect. — jiminny — app
Jiminny\Exceptions\SocialAccountTokenInvalidException: Your Salesforce account has become disconnected. Please login to Jiminny to reconnect. — jiminny — app
Allow owner's role to be selected when setting up a trial by LakyLak · Pull Request #12092 · jiminny/app
Allow owner's role to be selected when setting up a trial by LakyLak · Pull Request #12092 · jiminny/app
[SRD-6862] ‘User does not have any of the necessary access rights’ when trying to see another team’s performance scored with the AI ACS in team insights. - Jira
[SRD-6862] ‘User does not have any of the necessary access rights’ when trying to see another team’s performance scored with the AI ACS in team insights. - Jira
New Tab
New Tab
[JY-20912] Fallback mechanism for users with active SF tokens for CRM Matching - Jira
[JY-20912] Fallback mechanism for users with active SF tokens for CRM Matching - Jira
[JY-20771] Call Scoring filter for Exec reports - Jira
[JY-20771] Call Scoring filter for Exec reports - Jira
[JY-20878] SCIM > Allow customers to manage user roles through SCIM - Jira
[JY-20878] SCIM > Allow customers to manage user roles through SCIM - Jira
[JY-20879] Enable users to use their new activity types - Jira
[JY-20879] Enable users to use their new activity types - Jira
Project Phoenix – Figma
Project Phoenix – Figma
[JY-20847] Users can filter Scores in Team Insights by Host - Jira
[JY-20847] Users can filter Scores in Team Insights by Host - Jira
[JY-20534] AI Call Scoring quick access in Playback header - Jira
[JY-20534] AI Call Scoring quick access in Playback header - Jira
Close tab
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Sidebar
Sidebar
Top Bar
Top Bar
Main Content
Main Content
Collapse sidebar [
Collapse sidebar [
Switch sites or apps
Switch sites or apps
Go to your Jira homepage
Search, press enter to navigate to advanced search with your text query
Create
Create
Rovo Ask Rovo...
|
Firefox
|
[JY-20534] AI Call Scoring quick access in Playbac [JY-20534] AI Call Scoring quick access in Playback header - Jira — Work...
|
jiminny.atlassian.net/browse/JY-20534
|
54258
|
|
54259
|
Platform Sprint 4 Q2 - Platform Team - Scrum Board Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Usage | Windsurf
Usage | Windsurf
Allow owner's role to be selected when setting up a trial by LakyLak · Pull Request #12092 · jiminny/app
Allow owner's role to be selected when setting up a trial by LakyLak · Pull Request #12092 · jiminny/app
Pipelines - jiminny/app
Pipelines - jiminny/app
[SRD-6848] Sidekick SMS issue - Jira
[SRD-6848] Sidekick SMS issue - Jira
CloudWatch | us-east-2
CloudWatch | us-east-2
CloudWatch | us-east-2
CloudWatch | us-east-2
Jiminny
Jiminny
Jiminny\Exceptions\SocialAccountTokenInvalidException: Your Salesforce account has become disconnected. Please login to Jiminny to reconnect. — jiminny — app
Jiminny\Exceptions\SocialAccountTokenInvalidException: Your Salesforce account has become disconnected. Please login to Jiminny to reconnect. — jiminny — app
Allow owner's role to be selected when setting up a trial by LakyLak · Pull Request #12092 · jiminny/app
Allow owner's role to be selected when setting up a trial by LakyLak · Pull Request #12092 · jiminny/app
[SRD-6862] ‘User does not have any of the necessary access rights’ when trying to see another team’s performance scored with the AI ACS in team insights. - Jira
[SRD-6862] ‘User does not have any of the necessary access rights’ when trying to see another team’s performance scored with the AI ACS in team insights. - Jira
New Tab
New Tab
[JY-20912] Fallback mechanism for users with active SF tokens for CRM Matching - Jira
[JY-20912] Fallback mechanism for users with active SF tokens for CRM Matching - Jira
[JY-20771] Call Scoring filter for Exec reports - Jira
[JY-20771] Call Scoring filter for Exec reports - Jira
[JY-20878] SCIM > Allow customers to manage user roles through SCIM - Jira
[JY-20878] SCIM > Allow customers to manage user roles through SCIM - Jira
[JY-20879] Enable users to use their new activity types - Jira
[JY-20879] Enable users to use their new activity types - Jira
Project Phoenix – Figma
Project Phoenix – Figma
[JY-20847] Users can filter Scores in Team Insights by Host - Jira
[JY-20847] Users can filter Scores in Team Insights by Host - Jira
[JY-20534] AI Call Scoring quick access in Playback header - Jira
[JY-20534] AI Call Scoring quick access in Playback header - Jira
Close tab
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Sidebar
Sidebar
Top Bar
Top Bar
Main Content
Main Content
Collapse sidebar [
Collapse sidebar [
Switch sites or apps
Switch sites or apps
Go to your Jira homepage
Search, press enter to navigate to advanced search with your text query
Create...
|
Firefox
|
[JY-20534] AI Call Scoring quick access in Playbac [JY-20534] AI Call Scoring quick access in Playback header - Jira — Work...
|
jiminny.atlassian.net/browse/JY-20534
|
54259
|
|
54260
|
Platform Sprint 4 Q2 - Platform Team - Scrum Board Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 4 Q2 - Platform Team - Scrum Board - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Usage | Windsurf
Usage | Windsurf
Allow owner's role to be selected when setting up a trial by LakyLak · Pull Request #12092 · jiminny/app
Allow owner's role to be selected when setting up a trial by LakyLak · Pull Request #12092 · jiminny/app
Pipelines - jiminny/app
Pipelines - jiminny/app
[SRD-6848] Sidekick SMS issue - Jira
[SRD-6848] Sidekick SMS issue - Jira
CloudWatch | us-east-2
CloudWatch | us-east-2
CloudWatch | us-east-2
CloudWatch | us-east-2
Jiminny
Jiminny
Jiminny\Exceptions\SocialAccountTokenInvalidException: Your Salesforce account has become disconnected. Please login to Jiminny to reconnect. — jiminny — app
Jiminny\Exceptions\SocialAccountTokenInvalidException: Your Salesforce account has become disconnected. Please login to Jiminny to reconnect. — jiminny — app
Allow owner's role to be selected when setting up a trial by LakyLak · Pull Request #12092 · jiminny/app
Allow owner's role to be selected when setting up a trial by LakyLak · Pull Request #12092 · jiminny/app
[SRD-6862] ‘User does not have any of the necessary access rights’ when trying to see another team’s performance scored with the AI ACS in team insights. - Jira
[SRD-6862] ‘User does not have any of the necessary access rights’ when trying to see another team’s performance scored with the AI ACS in team insights. - Jira
New Tab
New Tab
[JY-20912] Fallback mechanism for users with active SF tokens for CRM Matching - Jira
[JY-20912] Fallback mechanism for users with active SF tokens for CRM Matching - Jira
[JY-20771] Call Scoring filter for Exec reports - Jira
[JY-20771] Call Scoring filter for Exec reports - Jira
[JY-20878] SCIM > Allow customers to manage user roles through SCIM - Jira
[JY-20878] SCIM > Allow customers to manage user roles through SCIM - Jira
[JY-20879] Enable users to use their new activity types - Jira
[JY-20879] Enable users to use their new activity types - Jira
Project Phoenix – Figma...
|
Firefox
|
[JY-20534] AI Call Scoring quick access in Playbac [JY-20534] AI Call Scoring quick access in Playback header - Jira — Work...
|
jiminny.atlassian.net/browse/JY-20534
|
54260
|
|
74345
|
Platform Team - Backlog - Jira
Service-Desk - Queu Platform Team - Backlog - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Feed — jiminny — Sentry
Feed — jiminny — Sentry
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Top Bar
Top Bar
Sidebar
Sidebar
Main Content
Main Content
Space navigation
Space navigation
Panel
Panel
Expand sidebar [
Expand sidebar [
Switch sites or apps
Switch sites or apps
Go to your Jira homepage
Search, press enter to navigate to advanced search with your text query
Create
Create
Rovo Ask Rovo
Ask Rovo
Notifications
Notifications
Help
Help
Settings
Settings
[EMAIL]
[EMAIL]
Spaces
Spaces
/
Jiminny (New)
Jiminny (New)
Platform Team
Platform Team
Add people
Add people
Board actions
Board actions
Share
Automation
Give feedback
Give feedback
Enter full screen
Enter full screen
Summary
Summary
Timeline
Timeline
Backlog
Backlog
Active sprints
Active sprints
Calendar
Calendar
Reports
Reports
Testing Board
Testing Board
List
List
Forms
Forms
Components
Components
Development
Development
Code
Code
Security
Security
Releases
Releases
Deployments
Deployments
Archived work items
Archived work items...
|
Firefox
|
Platform Team - Backlog - Jira — Work
|
jiminny.atlassian.net/browse/JY-20501
|
74345
|
|
74346
|
Platform Team - Backlog - Jira
Service-Desk - Queu Platform Team - Backlog - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Jira
Jira
Close tab
Feed — jiminny — Sentry
Feed — jiminny — Sentry
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Transferring data from jiminny.atlassian.net…...
|
Firefox
|
Jira — Work
|
jiminny.atlassian.net/browse/JY-20501
|
74346
|
|
74347
|
Platform Team - Backlog - Jira
Service-Desk - Queu Platform Team - Backlog - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Jira
Jira
Close tab
Feed — jiminny — Sentry
Feed — jiminny — Sentry
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Expand sidebar [
Expand sidebar [
The App Switcher is loading
Go to your Jira homepage
Search, press enter to navigate to advanced search with your text query
Create
Create
Rovo Ask Rovo
Ask Rovo
Notifications
Notifications
Help
Help
Settings
Settings
[EMAIL]
[EMAIL]
Spaces
Spaces
/
Jiminny (New) Jiminny (New)
Jiminny (New)
/
Epic - Change parent
JY-15971
JY-15971
/
Story - Change work type
JY-20501
JY-20501
Copy link
Batch initial sync for Hubspot- Summary, edit
Batch initial sync for Hubspot
Batch initial sync for Hubspot
Add or create work related to this Story
Add or create work related to this Story
View app actions
View app actions
Collapse Description Description
Collapse Description
Collapse Description
Description
Add Description, edit
Currently synching initial user profile (opportunities) is not working sufficiently when a huge amount of objects are imported from the CRM into Jiminny.
Problems:
Importing deals can take hours
Solution:
The current
syncOpportunities()
should only read the batches of deals from Hubspot and store the payload in Redis
There should be a separate job
import object
per batches of 100 updated deals which reads the info for objects from Redis and import them in Jiminny
There should be retry mechanism of the jobs so that in case they are using spot instance for processing which is turned off, the job will be retried
We should clean the Redis in 24 hours in case there are objects which are still not processed
Collapse Subtasks Subtasks Work item actions Create subtask
Collapse Subtasks
Collapse Subtasks
Subtasks
Work item actions
Work item actions
Create subtask
Create subtask
0
% Done
Work
Work
More actions for Work
More actions for Work
Priority
Priority
More actions for Priority
More actions for Priority
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Medium
Unassigned
Ready for Dev - Change status
READY FOR DEV
Work
Work
More actions for Work
More actions for Work
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Priority
Priority
More actions for Priority
More actions for Priority
Medium
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Unassigned
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
Ready for Dev - Change status
READY FOR DEV
Collapse Linked work items Linked work items Link a work item
Collapse Linked work items
Collapse Linked work items
Linked work items
Link a work item
Link a work item
clones
clones
JY-20500 is not done
JY-20500
Batch initial sync for Salesforce
Batch initial sync for Salesforce
Backlog - Change status
BACKLOG
Unlink work item
Collapse Activity Activity
Collapse Activity
Collapse Activity
Activity
All
All
Comments
Comments
History
History
Work log
Work log
Atlassian Intelligence Summarise
Summarise
Newest first Newest first
Newest first
Add a comment…
Suggest a reply...
Suggest a reply...
Who is working on this...?
Who is working on this...?
Status update...
Status update......
|
Firefox
|
Jira — Work
|
jiminny.atlassian.net/browse/JY-20501
|
74347
|
|
74348
|
Platform Team - Backlog - Jira
Service-Desk - Queu Platform Team - Backlog - Jira
Service-Desk - Queues - Platform team - Service space - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
Close tab
Feed — jiminny — Sentry
Feed — jiminny — Sentry
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Sidebar
Sidebar
Top Bar
Top Bar
Main Content
Main Content
Expand sidebar [
Expand sidebar [
Switch sites or apps
Switch sites or apps
Go to your Jira homepage
Search, press enter to navigate to advanced search with your text query
Create
Create
Rovo Ask Rovo
Ask Rovo
Notifications
Notifications
Help
Help
Settings
Settings
[EMAIL]
[EMAIL]
Spaces
Spaces
/
Jiminny (New) Jiminny (New)
Jiminny (New)
/
Epic - Change parent
JY-15971
JY-15971
/
Story - Change work type
JY-20501
JY-20501
Copy link
Batch initial sync for Hubspot- Summary, edit
Batch initial sync for Hubspot
Batch initial sync for Hubspot
Add or create work related to this Story
Add or create work related to this Story
View app actions
View app actions
Collapse Description Description
Collapse Description
Collapse Description
Description
Add Description, edit
Currently synching initial user profile (opportunities) is not working sufficiently when a huge amount of objects are imported from the CRM into Jiminny.
Problems:
Importing deals can take hours
Solution:
The current
syncOpportunities()
should only read the batches of deals from Hubspot and store the payload in Redis
There should be a separate job
import object
per batches of 100 updated deals which reads the info for objects from Redis and import them in Jiminny
There should be retry mechanism of the jobs so that in case they are using spot instance for processing which is turned off, the job will be retried
We should clean the Redis in 24 hours in case there are objects which are still not processed
Collapse Subtasks Subtasks Work item actions Create subtask
Collapse Subtasks
Collapse Subtasks
Subtasks
Work item actions
Work item actions
Create subtask
Create subtask
0
% Done
Work
Work
More actions for Work
More actions for Work
Priority
Priority
More actions for Priority
More actions for Priority
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Medium
Unassigned
Ready for Dev - Change status
READY FOR DEV
Work
Work
More actions for Work
More actions for Work
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Priority
Priority
More actions for Priority
More actions for Priority
Medium
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Unassigned
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
Ready for Dev - Change status
READY FOR DEV
Collapse Linked work items Linked work items Link a work item
Collapse Linked work items
Collapse Linked work items
Linked work items
Link a work item
Link a work item
clones
clones
JY-20500 is not done
JY-20500
Batch initial sync for Salesforce
Batch initial sync for Salesforce
Backlog - Change status
BACKLOG
Unlink work item
Collapse Activity Activity
Collapse Activity
Collapse Activity
Activity
All
All
Comments
Comments
History
History
Work log
Work log
Atlassian Intelligence Summarise
Summarise
Newest first Newest first
Newest first
Add a comment…
Suggest a reply...
Suggest a reply...
Who is working on this...?
Who is working on this...?
Status update...
Status update...
Pro tip:
press
M
to comment
More information about Nikolay Nikolov
More information about Nikolay Nikolov
Nikolay Nikolov
Copy link to comment
20 April 2026 at 14:24
BE 1, QA: 1
Reply
Add thumbs up reaction
Add reaction
Edit
More actions
More information about Nikolay Nikolov
More information about Nikolay Nikolov...
|
Firefox
|
[JY-20501] Batch initial sync for Hubspot - Jira — [JY-20501] Batch initial sync for Hubspot - Jira — Work...
|
jiminny.atlassian.net/browse/JY-20501
|
74348
|
|
74349
|
Platform Team - Backlog - Jira
Service-Desk - Queu Platform Team - Backlog - Jira
Service-Desk - Queues - Platform team - Service space - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
Close tab
Feed — jiminny — Sentry
Feed — jiminny — Sentry
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Sidebar
Sidebar
Top Bar
Top Bar
Main Content
Main Content
Expand sidebar [
Expand sidebar [
Switch sites or apps
Switch sites or apps
Go to your Jira homepage
Search, press enter to navigate to advanced search with your text query
Create
Create
Rovo Ask Rovo
Ask Rovo
Notifications
Notifications
Help
Help
Settings
Settings
[EMAIL]
[EMAIL]
Spaces
Spaces
/
Jiminny (New) Jiminny (New)
Jiminny (New)
/
Epic - Change parent
JY-15971
JY-15971
/
Story - Change work type
JY-20501
JY-20501
Copy link
Batch initial sync for Hubspot- Summary, edit
Batch initial sync for Hubspot
Batch initial sync for Hubspot
Add or create work related to this Story
Add or create work related to this Story
View app actions
View app actions
Collapse Description Description
Collapse Description
Collapse Description
Description
Edit Description, edit
Currently synching initial user profile (opportunities) is not working sufficiently when a huge amount of objects are imported from the CRM into Jiminny.
Problems:
Importing deals can take hours
Solution:
The current
syncOpportunities()
should only read the batches of deals from Hubspot and store the payload in Redis
There should be a separate job
import object
per batches of 100 updated deals which reads the info for objects from Redis and import them in Jiminny
There should be retry mechanism of the jobs so that in case they are using spot instance for processing which is turned off, the job will be retried
We should clean the Redis in 24 hours in case there are objects which are still not processed
Collapse Subtasks Subtasks Work item actions Configure columns Create subtask
Collapse Subtasks
Collapse Subtasks
Subtasks
Work item actions
Work item actions
Configure columns
Configure columns
Create subtask
Create subtask
0
% Done
Work
Work
More actions for Work
More actions for Work
Priority
Priority
More actions for Priority
More actions for Priority
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Medium
Unassigned
Ready for Dev - Change status
READY FOR DEV
Work
Work
More actions for Work
More actions for Work
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Priority
Priority
More actions for Priority
More actions for Priority
Medium
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Unassigned
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
Ready for Dev - Change status
READY FOR DEV
Collapse Linked work items Linked work items Link a work item
Collapse Linked work items
Collapse Linked work items
Linked work items
Link a work item
Link a work item
clones
clones
JY-20500 is not done
JY-20500
Batch initial sync for Salesforce
Batch initial sync for Salesforce
Backlog - Change status
BACKLOG...
|
Firefox
|
[JY-20501] Batch initial sync for Hubspot - Jira — [JY-20501] Batch initial sync for Hubspot - Jira — Work...
|
jiminny.atlassian.net/browse/JY-20501
|
74349
|
|
74350
|
Platform Team - Backlog - Jira
Service-Desk - Queu Platform Team - Backlog - Jira
Service-Desk - Queues - Platform team - Service space - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
Close tab
Feed — jiminny — Sentry
Feed — jiminny — Sentry
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Sidebar
Sidebar
Top Bar
Top Bar
Main Content
Main Content
Expand sidebar [
Expand sidebar [
Switch sites or apps
Switch sites or apps
Go to your Jira homepage
Search, press enter to navigate to advanced search with your text query
Create
Create
Rovo Ask Rovo
Ask Rovo
Notifications
Notifications
Help
Help
Settings
Settings
[EMAIL]
[EMAIL]
Spaces
Spaces
/
Jiminny (New) Jiminny (New)
Jiminny (New)
/
Epic - Change parent
JY-15971
JY-15971
/
Story - Change work type
JY-20501
JY-20501
Copy link
Batch initial sync for Hubspot- Summary, edit
Batch initial sync for Hubspot
Batch initial sync for Hubspot
Add or create work related to this Story
Add or create work related to this Story
View app actions
View app actions
Collapse Description Description
Collapse Description
Collapse Description
Description
Edit Description, edit
Currently synching initial user profile (opportunities) is not working sufficiently when a huge amount of objects are imported from the CRM into Jiminny.
Problems:
Importing deals can take hours
Solution:
The current
syncOpportunities()
should only read the batches of deals from Hubspot and store the payload in Redis
There should be a separate job
import object
per batches of 100 updated deals which reads the info for objects from Redis and import them in Jiminny
There should be retry mechanism of the jobs so that in case they are using spot instance for processing which is turned off, the job will be retried
We should clean the Redis in 24 hours in case there are objects which are still not processed
Collapse Subtasks Subtasks Work item actions Configure columns Create subtask
Collapse Subtasks
Collapse Subtasks
Subtasks
Work item actions
Work item actions
Configure columns
Configure columns
Create subtask
Create subtask
0
% Done
Work
Work
More actions for Work
More actions for Work
Priority
Priority
More actions for Priority
More actions for Priority
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Medium
Unassigned
Ready for Dev - Change status
READY FOR DEV
Work
Work
More actions for Work
More actions for Work
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Priority
Priority
More actions for Priority
More actions for Priority
Medium
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Unassigned
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
Ready for Dev - Change status
READY FOR DEV
Collapse Linked work items Linked work items Link a work item
Collapse Linked work items
Collapse Linked work items
Linked work items
Link a work item
Link a work item
clones
clones
JY-20500 is not done
JY-20500
Batch initial sync for Salesforce
Batch initial sync for Salesforce
Backlog - Change status
BACKLOG
Unlink work item
Collapse Activity Activity
Collapse Activity
Collapse Activity
Activity
All
All
Comments
Comments
History
History
Work log
Work log
Atlassian Intelligence Summarise
Summarise
Newest first Newest first
Newest first
Add a comment…
Suggest a reply...
Suggest a reply...
Who is working on this...?
Who is working on this...?
Status update...
Status update...
Pro tip:
press
M
to comment...
|
Firefox
|
[JY-20501] Batch initial sync for Hubspot - Jira — [JY-20501] Batch initial sync for Hubspot - Jira — Work...
|
jiminny.atlassian.net/browse/JY-20501
|
74350
|
|
74351
|
Platform Team - Backlog - Jira
Service-Desk - Queu Platform Team - Backlog - Jira
Service-Desk - Queues - Platform team - Service space - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
Close tab
Feed — jiminny — Sentry
Feed — jiminny — Sentry
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Sidebar
Sidebar
Top Bar
Top Bar
Main Content
Main Content
Expand sidebar [
Expand sidebar [
Switch sites or apps
Switch sites or apps
Go to your Jira homepage
Search, press enter to navigate to advanced search with your text query
Create
Create
Rovo Ask Rovo
Ask Rovo
Notifications
Notifications
Help
Help
Settings
Settings
[EMAIL]
[EMAIL]
Spaces
Spaces
/
Jiminny (New) Jiminny (New)
Jiminny (New)
/
Epic - Change parent
JY-15971
JY-15971
/
Story - Change work type
JY-20501
JY-20501
Copy link
Batch initial sync for Hubspot- Summary, edit
Batch initial sync for Hubspot
Batch initial sync for Hubspot
Add or create work related to this Story
Add or create work related to this Story
View app actions
View app actions
Collapse Description Description
Collapse Description
Collapse Description
Description
Edit Description, edit
Currently synching initial user profile (opportunities) is not working sufficiently when a huge amount of objects are imported from the CRM into Jiminny.
Problems:
Importing deals can take hours
Solution:
The current
syncOpportunities()
should only read the batches of deals from Hubspot and store the payload in Redis
There should be a separate job
import object
per batches of 100 updated deals which reads the info for objects from Redis and import them in Jiminny
There should be retry mechanism of the jobs so that in case they are using spot instance for processing which is turned off, the job will be retried
We should clean the Redis in 24 hours in case there are objects which are still not processed
Collapse Subtasks Subtasks Work item actions Configure columns Create subtask
Collapse Subtasks
Collapse Subtasks
Subtasks
Work item actions
Work item actions
Configure columns
Configure columns
Create subtask
Create subtask
0
% Done
Work
Work
More actions for Work
More actions for Work
Priority
Priority
More actions for Priority
More actions for Priority
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Edit Priority
Medium
Unassigned- edit Assignee
Unassigned
Ready for Dev - Change status
READY FOR DEV
Work
Work
More actions for Work
More actions for Work
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Priority
Priority
More actions for Priority
More actions for Priority
Edit Priority
Medium
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Unassigned- edit Assignee
Unassigned
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
Ready for Dev - Change status
READY FOR DEV
Collapse Linked work items Linked work items Link a work item
Collapse Linked work items
Collapse Linked work items
Linked work items
Link a work item
Link a work item
clones
clones
JY-20500 is not done
JY-20500
Batch initial sync for Salesforce
Batch initial sync for Salesforce
Backlog - Change status
BACKLOG
Unlink work item
Collapse Activity Activity
Collapse Activity
Collapse Activity
Activity
All
All
Comments
Comments
History
History
Work log
Work log
Atlassian Intelligence Summarise
Summarise
Newest first Newest first
Newest first
Add a comment…
Suggest a reply...
Suggest a reply...
Who is working on this...?
Who is working on this...?
Status update...
Status update...
Pro tip:
press
M
to comment
More information about Nikolay Nikolov
More information about Nikolay Nikolov
Nikolay Nikolov
Copy link to comment
20 April 2026 at 14:24
BE 1, QA: 1
Reply
Add thumbs up reaction
Add reaction
Edit
More actions...
|
Firefox
|
[JY-20501] Batch initial sync for Hubspot - Jira — [JY-20501] Batch initial sync for Hubspot - Jira — Work...
|
jiminny.atlassian.net/browse/JY-20501
|
74351
|
|
74352
|
Platform Team - Backlog - Jira
Service-Desk - Queu Platform Team - Backlog - Jira
Service-Desk - Queues - Platform team - Service space - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
Close tab
Feed — jiminny — Sentry
Feed — jiminny — Sentry
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Sidebar
Sidebar
Top Bar
Top Bar
Main Content
Main Content
Expand sidebar [
Expand sidebar [
Switch sites or apps
Switch sites or apps
Go to your Jira homepage
Search, press enter to navigate to advanced search with your text query
Create
Create
Rovo Ask Rovo
Ask Rovo
Notifications
Notifications
Help
Help
Settings
Settings
[EMAIL]
[EMAIL]
Spaces
Spaces
/
Jiminny (New) Jiminny (New)
Jiminny (New)
/
Epic - Change parent
JY-15971
JY-15971
/
Story - Change work type
JY-20501
JY-20501
Copy link
Batch initial sync for Hubspot- Summary, edit
Batch initial sync for Hubspot
Batch initial sync for Hubspot
Add or create work related to this Story
Add or create work related to this Story
View app actions
View app actions
Collapse Description Description
Collapse Description
Collapse Description
Description
Edit Description, edit
Currently synching initial user profile (opportunities) is not working sufficiently when a huge amount of objects are imported from the CRM into Jiminny.
Problems:
Importing deals can take hours
Solution:
The current
syncOpportunities()
should only read the batches of deals from Hubspot and store the payload in Redis
There should be a separate job
import object
per batches of 100 updated deals which reads the info for objects from Redis and import them in Jiminny
There should be retry mechanism of the jobs so that in case they are using spot instance for processing which is turned off, the job will be retried
We should clean the Redis in 24 hours in case there are objects which are still not processed
Collapse Subtasks Subtasks Work item actions Configure columns Create subtask
Collapse Subtasks
Collapse Subtasks
Subtasks
Work item actions
Work item actions
Configure columns
Configure columns
Create subtask
Create subtask
0
% Done
Work
Work
More actions for Work
More actions for Work
Priority
Priority
More actions for Priority
More actions for Priority
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Edit Priority
Medium
Unassigned- edit Assignee
Unassigned
Ready for Dev - Change status
READY FOR DEV
Work
Work
More actions for Work
More actions for Work
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Priority
Priority
More actions for Priority
More actions for Priority
Edit Priority
Medium
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Unassigned- edit Assignee
Unassigned
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
Ready for Dev - Change status
READY FOR DEV
Collapse Linked work items Linked work items Link a work item
Collapse Linked work items
Collapse Linked work items
Linked work items
Link a work item
Link a work item
clones
clones
JY-20500 is not done
JY-20500
Batch initial sync for Salesforce
Batch initial sync for Salesforce
Backlog - Change status
BACKLOG
Unlink work item
Collapse Activity Activity
Collapse Activity
Collapse Activity
Activity
All
All
Comments
Comments
History
History
Work log
Work log
Atlassian Intelligence Summarise
Summarise
Newest first Newest first
Newest first
Add a comment…
Suggest a reply...
Suggest a reply...
Who is working on this...?
Who is working on this...?
Status update...
Status update...
Pro tip:
press
M
to comment
More information about Nikolay Nikolov
More information about Nikolay Nikolov
Nikolay Nikolov
Copy link to comment
20 April 2026 at 14:24
BE 1, QA: 1
Reply
Add thumbs up reaction
Add reaction
Edit
More actions
More information about Nikolay Nikolov
More information about Nikolay Nikolov
Nikolay Nikolov
Copy link to comment
20 April 2026 at 14:07
Initial Owner/Profile Sync for Opportunities
Initial Owner/Profile Sync for Opportunities
Where It Happens
Where It Happens
Trigger:
ProfileCreated
event →
SyncProfileOpportunities
listener
Turn on wrap
Copy as text
1
User connects to CRM → Profile created → ProfileCreated event
2
↓
3
SyncProfileOpportunities::handle()
4
↓
5
SyncOpportunitiesJob dispatched
Location
Location
SyncProfileOpportunities.php
How It Works
How It Works
Step
Action
1
ProfileCreated
event fires when a new CRM profile is created
2
SyncProfileOpportunities
listener handles it
3
Dispatches
SyncOpportunitiesJob
with
crm_profile_id
parameter
4
Uses
LAST_MODIFIED_BY_PROFILE_SYNC_OPPORTUNITY_STRATEGY
Step
1
2
3
4
Action
ProfileCreated
event fires when a new CRM profile is created
SyncProfileOpportunities
listener handles it
Dispatches
SyncOpportunitiesJob
with
crm_profile_id
parameter
Uses
LAST_MODIFIED_BY_PROFILE_SYNC_OPPORTUNITY_STRATEGY
Providers Supported (lines 51-61)
Providers Supported (lines 51-61)
HubSpot
Salesforce
Batching?...
|
Firefox
|
[JY-20501] Batch initial sync for Hubspot - Jira — [JY-20501] Batch initial sync for Hubspot - Jira — Work...
|
jiminny.atlassian.net/browse/JY-20501
|
74352
|
|
74353
|
Platform Team - Backlog - Jira
Service-Desk - Queu Platform Team - Backlog - Jira
Service-Desk - Queues - Platform team - Service space - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
Close tab
Feed — jiminny — Sentry
Feed — jiminny — Sentry
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Sidebar
Sidebar
Top Bar
Top Bar
Main Content
Main Content
Expand sidebar [
Expand sidebar [
Switch sites or apps
Switch sites or apps
Go to your Jira homepage
Search, press enter to navigate to advanced search with your text query
Create
Create
Rovo Ask Rovo
Ask Rovo
Notifications
Notifications
Help
Help
Settings
Settings
[EMAIL]
[EMAIL]
Spaces
Spaces
/
Jiminny (New) Jiminny (New)
Jiminny (New)
/
Epic - Change parent
JY-15971
JY-15971
/
Story - Change work type
JY-20501
JY-20501
Copy link
Batch initial sync for Hubspot- Summary, edit
Batch initial sync for Hubspot
Batch initial sync for Hubspot
Add or create work related to this Story
Add or create work related to this Story
View app actions
View app actions
Collapse Description Description
Collapse Description
Collapse Description
Description
Edit Description, edit
Currently synching initial user profile (opportunities) is not working sufficiently when a huge amount of objects are imported from the CRM into Jiminny.
Problems:
Importing deals can take hours
Solution:
The current
syncOpportunities()
should only read the batches of deals from Hubspot and store the payload in Redis
There should be a separate job
import object
per batches of 100 updated deals which reads the info for objects from Redis and import them in Jiminny
There should be retry mechanism of the jobs so that in case they are using spot instance for processing which is turned off, the job will be retried
We should clean the Redis in 24 hours in case there are objects which are still not processed
Collapse Subtasks Subtasks Work item actions Configure columns Create subtask
Collapse Subtasks
Collapse Subtasks
Subtasks
Work item actions
Work item actions
Configure columns
Configure columns
Create subtask
Create subtask
0
% Done
Work
Work
More actions for Work
More actions for Work
Priority
Priority
More actions for Priority
More actions for Priority
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Edit Priority
Medium
Unassigned- edit Assignee
Unassigned
Ready for Dev - Change status
READY FOR DEV
Work
Work
More actions for Work
More actions for Work
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Priority
Priority
More actions for Priority
More actions for Priority
Edit Priority
Medium
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Unassigned- edit Assignee
Unassigned
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
Ready for Dev - Change status
READY FOR DEV
Collapse Linked work items Linked work items Link a work item
Collapse Linked work items
Collapse Linked work items
Linked work items
Link a work item
Link a work item
clones
clones
JY-20500 is not done
JY-20500
Batch initial sync for Salesforce
Batch initial sync for Salesforce
Backlog - Change status
BACKLOG
Unlink work item
Collapse Activity Activity
Collapse Activity
Collapse Activity
Activity
All
All
Comments
Comments
History
History
Work log
Work log
Atlassian Intelligence Summarise
Summarise
Newest first Newest first
Newest first
Add a comment…
Suggest a reply...
Suggest a reply...
Who is working on this...?
Who is working on this...?
Status update...
Status update...
Pro tip:
press
M
to comment
More information about Nikolay Nikolov
More information about Nikolay Nikolov
Nikolay Nikolov
Copy link to comment
20 April 2026 at 14:24
BE 1, QA: 1
Reply
Add thumbs up reaction
Add reaction
Edit
More actions
More information about Nikolay Nikolov
More information about Nikolay Nikolov
Nikolay Nikolov
Copy link to comment
20 April 2026 at 14:07
Initial Owner/Profile Sync for Opportunities
Initial Owner/Profile Sync for Opportunities
Where It Happens
Where It Happens
Trigger:
ProfileCreated
event →
SyncProfileOpportunities
listener
Turn on wrap
Copy as text
1
User connects to CRM → Profile created → ProfileCreated event
2
↓
3
SyncProfileOpportunities::handle()
4
↓
5
SyncOpportunitiesJob dispatched
Location
Location
SyncProfileOpportunities.php
How It Works
How It Works
Step
Action
1
ProfileCreated
event fires when a new CRM profile is created
2
SyncProfileOpportunities
listener handles it
3
Dispatches
SyncOpportunitiesJob
with
crm_profile_id
parameter
4
Uses
LAST_MODIFIED_BY_PROFILE_SYNC_OPPORTUNITY_STRATEGY
Step
1
2
3
4...
|
Firefox
|
[JY-20501] Batch initial sync for Hubspot - Jira — [JY-20501] Batch initial sync for Hubspot - Jira — Work...
|
jiminny.atlassian.net/browse/JY-20501
|
74353
|
|
74354
|
Platform Team - Backlog - Jira
Service-Desk - Queu Platform Team - Backlog - Jira
Service-Desk - Queues - Platform team - Service space - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
Close tab
Feed — jiminny — Sentry
Feed — jiminny — Sentry
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Sidebar
Sidebar
Top Bar
Top Bar
Main Content
Main Content
Expand sidebar [
Expand sidebar [
Switch sites or apps
Switch sites or apps
Go to your Jira homepage
Search, press enter to navigate to advanced search with your text query
Create
Create
Rovo Ask Rovo
Ask Rovo
Notifications
Notifications
Help
Help
Settings
Settings
[EMAIL]
[EMAIL]
Spaces
Spaces
/
Jiminny (New) Jiminny (New)
Jiminny (New)
/
Epic - Change parent
JY-15971
JY-15971
/
Story - Change work type
JY-20501
JY-20501
Copy link
Batch initial sync for Hubspot- Summary, edit
Batch initial sync for Hubspot
Batch initial sync for Hubspot
Add or create work related to this Story
Add or create work related to this Story
View app actions
View app actions
Collapse Description Description
Collapse Description
Collapse Description
Description
Edit Description, edit
Currently synching initial user profile (opportunities) is not working sufficiently when a huge amount of objects are imported from the CRM into Jiminny.
Problems:
Importing deals can take hours
Solution:
The current
syncOpportunities()
should only read the batches of deals from Hubspot and store the payload in Redis
There should be a separate job
import object
per batches of 100 updated deals which reads the info for objects from Redis and import them in Jiminny
There should be retry mechanism of the jobs so that in case they are using spot instance for processing which is turned off, the job will be retried
We should clean the Redis in 24 hours in case there are objects which are still not processed
Collapse Subtasks Subtasks Work item actions Configure columns Create subtask
Collapse Subtasks
Collapse Subtasks
Subtasks
Work item actions
Work item actions
Configure columns
Configure columns
Create subtask
Create subtask
0
% Done
Work
Work
More actions for Work
More actions for Work
Priority
Priority
More actions for Priority
More actions for Priority
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Edit Priority
Medium
Unassigned- edit Assignee
Unassigned
Ready for Dev - Change status
READY FOR DEV
Work
Work
More actions for Work
More actions for Work
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Priority
Priority
More actions for Priority
More actions for Priority
Edit Priority
Medium
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Unassigned- edit Assignee
Unassigned
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
Ready for Dev - Change status
READY FOR DEV
Collapse Linked work items Linked work items Link a work item
Collapse Linked work items
Collapse Linked work items
Linked work items
Link a work item
Link a work item
clones
clones
JY-20500 is not done
JY-20500
Batch initial sync for Salesforce
Batch initial sync for Salesforce
Backlog - Change status
BACKLOG
Unlink work item
Collapse Activity Activity
Collapse Activity
Collapse Activity
Activity
All
All
Comments
Comments
History
History
Work log
Work log
Atlassian Intelligence Summarise
Summarise
Newest first Newest first
Newest first
Add a comment…
Suggest a reply...
Suggest a reply...
Who is working on this...?
Who is working on this...?
Status update...
Status update......
|
Firefox
|
[JY-20501] Batch initial sync for Hubspot - Jira — [JY-20501] Batch initial sync for Hubspot - Jira — Work...
|
jiminny.atlassian.net/browse/JY-20501
|
74354
|
|
74355
|
Platform Team - Backlog - Jira
Service-Desk - Queu Platform Team - Backlog - Jira
Service-Desk - Queues - Platform team - Service space - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
Close tab
Feed — jiminny — Sentry
Feed — jiminny — Sentry
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Sidebar
Sidebar
Top Bar
Top Bar
Main Content
Main Content
Expand sidebar [
Expand sidebar [
Switch sites or apps
Switch sites or apps
Go to your Jira homepage
Search, press enter to navigate to advanced search with your text query
Create
Create
Rovo Ask Rovo
Ask Rovo
Notifications
Notifications
Help
Help
Settings
Settings
[EMAIL]
[EMAIL]
Spaces
Spaces
/
Jiminny (New) Jiminny (New)
Jiminny (New)
/
Epic - Change parent
JY-15971
JY-15971
/
Story - Change work type
JY-20501
JY-20501
Copy link
Batch initial sync for Hubspot- Summary, edit
Batch initial sync for Hubspot
Batch initial sync for Hubspot
Add or create work related to this Story
Add or create work related to this Story
View app actions
View app actions
Collapse Description Description
Collapse Description
Collapse Description
Description
Edit Description, edit
Currently synching initial user profile (opportunities) is not working sufficiently when a huge amount of objects are imported from the CRM into Jiminny.
Problems:
Importing deals can take hours
Solution:
The current
syncOpportunities()
should only read the batches of deals from Hubspot and store the payload in Redis
There should be a separate job
import object
per batches of 100 updated deals which reads the info for objects from Redis and import them in Jiminny
There should be retry mechanism of the jobs so that in case they are using spot instance for processing which is turned off, the job will be retried
We should clean the Redis in 24 hours in case there are objects which are still not processed
Collapse Subtasks Subtasks Work item actions Configure columns Create subtask
Collapse Subtasks
Collapse Subtasks
Subtasks
Work item actions
Work item actions
Configure columns
Configure columns
Create subtask
Create subtask
0
% Done
Work
Work
More actions for Work
More actions for Work
Priority
Priority
More actions for Priority
More actions for Priority
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Edit Priority
Medium
Unassigned- edit Assignee
Unassigned
Ready for Dev - Change status
READY FOR DEV
Work
Work
More actions for Work
More actions for Work
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Priority
Priority
More actions for Priority
More actions for Priority
Edit Priority
Medium
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Unassigned- edit Assignee
Unassigned
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
Ready for Dev - Change status
READY FOR DEV
Collapse Linked work items Linked work items Link a work item
Collapse Linked work items
Collapse Linked work items
Linked work items
Link a work item
Link a work item
clones
clones
JY-20500 is not done
JY-20500
Batch initial sync for Salesforce
Batch initial sync for Salesforce
Backlog - Change status
BACKLOG
Unlink work item
Collapse Activity Activity
Collapse Activity
Collapse Activity
Activity
All
All
Comments
Comments
History
History
Work log
Work log
Atlassian Intelligence Summarise
Summarise
Newest first Newest first
Newest first
Add a comment…
Suggest a reply...
Suggest a reply...
Who is working on this...?
Who is working on this...?
Status update...
Status update...
Pro tip:
press
M
to comment
More information about Nikolay Nikolov
More information about Nikolay Nikolov
Nikolay Nikolov
Copy link to comment
20 April 2026 at 14:24
BE 1, QA: 1
Reply
Add thumbs up reaction
Add reaction
Edit
More actions
More information about Nikolay Nikolov
More information about Nikolay Nikolov
Nikolay Nikolov
Copy link to comment
20 April 2026 at 14:07
Initial Owner/Profile Sync for Opportunities
Initial Owner/Profile Sync for Opportunities
Where It Happens
Where It Happens
Trigger:
ProfileCreated
event →
SyncProfileOpportunities
listener
Turn on wrap
Copy as text
1
User connects to CRM → Profile created → ProfileCreated event
2
↓
3
SyncProfileOpportunities::handle()
4
↓
5
SyncOpportunitiesJob dispatched
Location
Location
SyncProfileOpportunities.php
How It Works
How It Works
Step
Action
1...
|
Firefox
|
[JY-20501] Batch initial sync for Hubspot - Jira — [JY-20501] Batch initial sync for Hubspot - Jira — Work...
|
jiminny.atlassian.net/browse/JY-20501
|
74355
|
|
74356
|
Platform Team - Backlog - Jira
Service-Desk - Queu Platform Team - Backlog - Jira
Service-Desk - Queues - Platform team - Service space - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
Close tab
Feed — jiminny — Sentry
Feed — jiminny — Sentry
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Sidebar
Sidebar
Top Bar
Top Bar
Main Content
Main Content
Expand sidebar [
Expand sidebar [
Switch sites or apps
Switch sites or apps
Go to your Jira homepage
Search, press enter to navigate to advanced search with your text query
Create
Create
Rovo Ask Rovo
Ask Rovo
Notifications
Notifications
Help
Help
Settings
Settings
[EMAIL]
[EMAIL]
Spaces
Spaces
/
Jiminny (New) Jiminny (New)
Jiminny (New)
/
Epic - Change parent
JY-15971
JY-15971
/
Story - Change work type
JY-20501
JY-20501
Copy link
Batch initial sync for Hubspot- Summary, edit
Batch initial sync for Hubspot
Batch initial sync for Hubspot
Add or create work related to this Story
Add or create work related to this Story
View app actions
View app actions
Collapse Description Description
Collapse Description
Collapse Description
Description
Edit Description, edit
Currently synching initial user profile (opportunities) is not working sufficiently when a huge amount of objects are imported from the CRM into Jiminny.
Problems:
Importing deals can take hours
Solution:
The current
syncOpportunities()
should only read the batches of deals from Hubspot and store the payload in Redis
There should be a separate job
import object
per batches of 100 updated deals which reads the info for objects from Redis and import them in Jiminny
There should be retry mechanism of the jobs so that in case they are using spot instance for processing which is turned off, the job will be retried
We should clean the Redis in 24 hours in case there are objects which are still not processed
Collapse Subtasks Subtasks Work item actions Configure columns Create subtask
Collapse Subtasks
Collapse Subtasks
Subtasks
Work item actions
Work item actions
Configure columns
Configure columns
Create subtask
Create subtask
0
% Done
Work
Work
More actions for Work
More actions for Work
Priority
Priority
More actions for Priority
More actions for Priority
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Edit Priority
Medium
Unassigned- edit Assignee
Unassigned
Ready for Dev - Change status
READY FOR DEV
Work
Work
More actions for Work
More actions for Work
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Priority
Priority
More actions for Priority
More actions for Priority
Edit Priority
Medium
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Unassigned- edit Assignee
Unassigned
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
Ready for Dev - Change status
READY FOR DEV
Collapse Linked work items Linked work items Link a work item
Collapse Linked work items
Collapse Linked work items
Linked work items
Link a work item
Link a work item
clones
clones
JY-20500 is not done
JY-20500
Batch initial sync for Salesforce
Batch initial sync for Salesforce
Backlog - Change status
BACKLOG
Unlink work item
Collapse Activity Activity
Collapse Activity
Collapse Activity
Activity
All
All
Comments
Comments
History
History
Work log
Work log
Atlassian Intelligence Summarise
Summarise
Newest first Newest first
Newest first
Add a comment…
Suggest a reply...
Suggest a reply...
Who is working on this...?
Who is working on this...?
Status update...
Status update...
Pro tip:
press
M
to comment
More information about Nikolay Nikolov
More information about Nikolay Nikolov
Nikolay Nikolov
Copy link to comment
20 April 2026 at 14:24
BE 1, QA: 1
Reply
Add thumbs up reaction
Add reaction
Edit
More actions
More information about Nikolay Nikolov
More information about Nikolay Nikolov
Nikolay Nikolov
Copy link to comment
20 April 2026 at 14:07
Initial Owner/Profile Sync for Opportunities
Initial Owner/Profile Sync for Opportunities
Where It Happens
Where It Happens
Trigger:
ProfileCreated
event →
SyncProfileOpportunities
listener
Turn on wrap
Copy as text
1
User connects to CRM → Profile created → ProfileCreated event
2
↓
3
SyncProfileOpportunities::handle()
4
↓
5
SyncOpportunitiesJob dispatched
Location
Location
SyncProfileOpportunities.php
How It Works
How It Works
Step
Action
1
ProfileCreated
event fires when a new CRM profile is created
2
SyncProfileOpportunities
listener handles it
3
Dispatches...
|
Firefox
|
[JY-20501] Batch initial sync for Hubspot - Jira — [JY-20501] Batch initial sync for Hubspot - Jira — Work...
|
jiminny.atlassian.net/browse/JY-20501
|
74356
|
|
74357
|
Platform Team - Backlog - Jira
Service-Desk - Queu Platform Team - Backlog - Jira
Service-Desk - Queues - Platform team - Service space - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
Close tab
Feed — jiminny — Sentry
Feed — jiminny — Sentry
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Sidebar
Sidebar
Top Bar
Top Bar
Main Content
Main Content
Expand sidebar [
Expand sidebar [
Switch sites or apps
Switch sites or apps
Go to your Jira homepage
Search, press enter to navigate to advanced search with your text query
Create
Create
Rovo Ask Rovo
Ask Rovo
Notifications
Notifications
Help
Help
Settings
Settings
[EMAIL]
[EMAIL]
Spaces
Spaces
/
Jiminny (New) Jiminny (New)
Jiminny (New)
/
Epic - Change parent
JY-15971
JY-15971
/
Story - Change work type
JY-20501
JY-20501
Copy link
Batch initial sync for Hubspot- Summary, edit
Batch initial sync for Hubspot
Batch initial sync for Hubspot
Add or create work related to this Story
Add or create work related to this Story
View app actions
View app actions
Collapse Description Description
Collapse Description
Collapse Description
Description
Edit Description, edit
Currently synching initial user profile (opportunities) is not working sufficiently when a huge amount of objects are imported from the CRM into Jiminny.
Problems:
Importing deals can take hours
Solution:
The current
syncOpportunities()
should only read the batches of deals from Hubspot and store the payload in Redis
There should be a separate job
import object
per batches of 100 updated deals which reads the info for objects from Redis and import them in Jiminny
There should be retry mechanism of the jobs so that in case they are using spot instance for processing which is turned off, the job will be retried
We should clean the Redis in 24 hours in case there are objects which are still not processed
Collapse Subtasks Subtasks Work item actions Configure columns Create subtask
Collapse Subtasks
Collapse Subtasks
Subtasks
Work item actions
Work item actions
Configure columns
Configure columns
Create subtask
Create subtask
0
% Done
Work
Work
More actions for Work
More actions for Work
Priority
Priority
More actions for Priority
More actions for Priority
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Edit Priority
Medium
Unassigned- edit Assignee
Unassigned
Ready for Dev - Change status
READY FOR DEV
Work
Work
More actions for Work
More actions for Work
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Priority
Priority
More actions for Priority
More actions for Priority
Edit Priority
Medium
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Unassigned- edit Assignee
Unassigned
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
Ready for Dev - Change status
READY FOR DEV
Collapse Linked work items Linked work items Link a work item
Collapse Linked work items
Collapse Linked work items
Linked work items
Link a work item
Link a work item
clones
clones
JY-20500 is not done
JY-20500
Batch initial sync for Salesforce
Batch initial sync for Salesforce
Backlog - Change status
BACKLOG
Unlink work item
Collapse Activity Activity
Collapse Activity
Collapse Activity
Activity
All
All
Comments
Comments
History
History
Work log
Work log
Atlassian Intelligence Summarise
Summarise
Newest first Newest first
Newest first
Add a comment…
Suggest a reply...
Suggest a reply...
Who is working on this...?
Who is working on this...?
Status update...
Status update...
Pro tip:
press
M
to comment
More information about Nikolay Nikolov
More information about Nikolay Nikolov
Nikolay Nikolov
Copy link to comment
20 April 2026 at 14:24
BE 1, QA: 1
Reply
Add thumbs up reaction
Add reaction
Edit
More actions
More information about Nikolay Nikolov
More information about Nikolay Nikolov
Nikolay Nikolov
Copy link to comment
20 April 2026 at 14:07
Initial Owner/Profile Sync for Opportunities
Initial Owner/Profile Sync for Opportunities
Where It Happens
Where It Happens
Trigger:
ProfileCreated
event →
SyncProfileOpportunities
listener
Turn on wrap
Copy as text
1
User connects to CRM → Profile created → ProfileCreated event
2
↓
3
SyncProfileOpportunities::handle()
4
↓
5
SyncOpportunitiesJob dispatched
Location
Location
SyncProfileOpportunities.php
How It Works
How It Works
Step
Action
1
ProfileCreated
event fires when a new CRM profile is created
2
SyncProfileOpportunities
listener handles it
3
Dispatches
SyncOpportunitiesJob
with
crm_profile_id
parameter
4
Uses
LAST_MODIFIED_BY_PROFILE_SYNC_OPPORTUNITY_STRATEGY
Step...
|
Firefox
|
[JY-20501] Batch initial sync for Hubspot - Jira — [JY-20501] Batch initial sync for Hubspot - Jira — Work...
|
jiminny.atlassian.net/browse/JY-20501
|
74357
|
|
74358
|
Platform Team - Backlog - Jira
Service-Desk - Queu Platform Team - Backlog - Jira
Service-Desk - Queues - Platform team - Service space - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
Close tab
Feed — jiminny — Sentry
Feed — jiminny — Sentry
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Sidebar
Sidebar
Top Bar
Top Bar
Main Content
Main Content
Expand sidebar [
Expand sidebar [
Switch sites or apps
Switch sites or apps
Go to your Jira homepage
Search, press enter to navigate to advanced search with your text query
Create
Create
Rovo Ask Rovo
Ask Rovo
Notifications
Notifications
Help
Help
Settings
Settings
[EMAIL]
[EMAIL]
Spaces
Spaces
/
Jiminny (New) Jiminny (New)
Jiminny (New)
/
Epic - Change parent
JY-15971
JY-15971
/
Story - Change work type
JY-20501
JY-20501
Copy link
Batch initial sync for Hubspot- Summary, edit
Batch initial sync for Hubspot
Batch initial sync for Hubspot
Add or create work related to this Story
Add or create work related to this Story
View app actions
View app actions
Collapse Description Description
Collapse Description
Collapse Description
Description
Edit Description, edit
Currently synching initial user profile (opportunities) is not working sufficiently when a huge amount of objects are imported from the CRM into Jiminny.
Problems:
Importing deals can take hours
Solution:
The current
syncOpportunities()
should only read the batches of deals from Hubspot and store the payload in Redis
There should be a separate job
import object
per batches of 100 updated deals which reads the info for objects from Redis and import them in Jiminny
There should be retry mechanism of the jobs so that in case they are using spot instance for processing which is turned off, the job will be retried
We should clean the Redis in 24 hours in case there are objects which are still not processed
Collapse Subtasks Subtasks Work item actions Configure columns Create subtask
Collapse Subtasks
Collapse Subtasks
Subtasks
Work item actions
Work item actions
Configure columns
Configure columns
Create subtask
Create subtask
0
% Done
Work
Work
More actions for Work
More actions for Work
Priority
Priority
More actions for Priority
More actions for Priority
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Edit Priority
Medium
Unassigned- edit Assignee
Unassigned
Ready for Dev - Change status
READY FOR DEV
Work
Work
More actions for Work
More actions for Work
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Priority
Priority
More actions for Priority
More actions for Priority
Edit Priority
Medium
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Unassigned- edit Assignee
Unassigned
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
Ready for Dev - Change status
READY FOR DEV
Collapse Linked work items Linked work items Link a work item
Collapse Linked work items
Collapse Linked work items
Linked work items
Link a work item
Link a work item
clones
clones
JY-20500 is not done
JY-20500
Batch initial sync for Salesforce
Batch initial sync for Salesforce
Backlog - Change status
BACKLOG
Unlink work item
Collapse Activity Activity
Collapse Activity
Collapse Activity
Activity
All
All
Comments
Comments
History
History
Work log
Work log
Atlassian Intelligence Summarise...
|
Firefox
|
[JY-20501] Batch initial sync for Hubspot - Jira — [JY-20501] Batch initial sync for Hubspot - Jira — Work...
|
jiminny.atlassian.net/browse/JY-20501
|
74358
|
|
74359
|
Platform Team - Backlog - Jira
Service-Desk - Queu Platform Team - Backlog - Jira
Service-Desk - Queues - Platform team - Service space - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
Close tab
Feed — jiminny — Sentry
Feed — jiminny — Sentry
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Sidebar
Sidebar
Top Bar
Top Bar
Main Content
Main Content
Expand sidebar [
Expand sidebar [
Switch sites or apps
Switch sites or apps
Go to your Jira homepage
Search, press enter to navigate to advanced search with your text query
Create
Create
Rovo Ask Rovo
Ask Rovo
Notifications
Notifications
Help
Help
Settings
Settings
[EMAIL]
[EMAIL]
Spaces
Spaces
/
Jiminny (New) Jiminny (New)
Jiminny (New)
/
Epic - Change parent
JY-15971
JY-15971
/
Story - Change work type
JY-20501
JY-20501
Copy link
Batch initial sync for Hubspot- Summary, edit
Batch initial sync for Hubspot
Batch initial sync for Hubspot
Add or create work related to this Story
Add or create work related to this Story
View app actions
View app actions
Collapse Description Description
Collapse Description
Collapse Description
Description
Edit Description, edit
Currently synching initial user profile (opportunities) is not working sufficiently when a huge amount of objects are imported from the CRM into Jiminny.
Problems:
Importing deals can take hours
Solution:
The current
syncOpportunities()
should only read the batches of deals from Hubspot and store the payload in Redis
There should be a separate job
import object
per batches of 100 updated deals which reads the info for objects from Redis and import them in Jiminny
There should be retry mechanism of the jobs so that in case they are using spot instance for processing which is turned off, the job will be retried
We should clean the Redis in 24 hours in case there are objects which are still not processed
Collapse Subtasks Subtasks Work item actions Configure columns Create subtask
Collapse Subtasks
Collapse Subtasks
Subtasks
Work item actions
Work item actions
Configure columns
Configure columns
Create subtask
Create subtask
0
% Done
Work
Work
More actions for Work
More actions for Work
Priority
Priority
More actions for Priority
More actions for Priority
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Status
Status
Status • Sort in ascending order...
|
Firefox
|
[JY-20501] Batch initial sync for Hubspot - Jira — [JY-20501] Batch initial sync for Hubspot - Jira — Work...
|
jiminny.atlassian.net/browse/JY-20501
|
74359
|
|
74360
|
Platform Team - Backlog - Jira
Service-Desk - Queu Platform Team - Backlog - Jira
Service-Desk - Queues - Platform team - Service space - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
Close tab
Feed — jiminny — Sentry
Feed — jiminny — Sentry
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Sidebar
Sidebar
Top Bar
Top Bar
Main Content
Main Content
Expand sidebar [
Expand sidebar [
Switch sites or apps
Switch sites or apps
Go to your Jira homepage
Search, press enter to navigate to advanced search with your text query
Create
Create
Rovo Ask Rovo
Ask Rovo
Notifications
Notifications
Help
Help
Settings
Settings
[EMAIL]
[EMAIL]
Spaces
Spaces
/
Jiminny (New) Jiminny (New)
Jiminny (New)
/
Epic - Change parent
JY-15971
JY-15971
/
Story - Change work type
JY-20501
JY-20501
Copy link
Batch initial sync for Hubspot- Summary, edit
Batch initial sync for Hubspot
Batch initial sync for Hubspot
Add or create work related to this Story
Add or create work related to this Story
View app actions
View app actions
Collapse Description Description
Collapse Description
Collapse Description
Description
Edit Description, edit
Currently synching initial user profile (opportunities) is not working sufficiently when a huge amount of objects are imported from the CRM into Jiminny.
Problems:
Importing deals can take hours
Solution:
The current
syncOpportunities()
should only read the batches of deals from Hubspot and store the payload in Redis
There should be a separate job
import object
per batches of 100 updated deals which reads the info for objects from Redis and import them in Jiminny
There should be retry mechanism of the jobs so that in case they are using spot instance for processing which is turned off, the job will be retried
We should clean the Redis in 24 hours in case there are objects which are still not processed
Collapse Subtasks Subtasks Work item actions Configure columns Create subtask
Collapse Subtasks
Collapse Subtasks
Subtasks
Work item actions
Work item actions
Configure columns
Configure columns
Create subtask
Create subtask
0
% Done
Work
Work
More actions for Work
More actions for Work
Priority
Priority
More actions for Priority
More actions for Priority
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Edit Priority
Medium
Unassigned- edit Assignee
Unassigned
Ready for Dev - Change status
READY FOR DEV
Work
Work
More actions for Work
More actions for Work
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Priority
Priority
More actions for Priority
More actions for Priority
Edit Priority
Medium
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Unassigned- edit Assignee
Unassigned
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
Ready for Dev - Change status
READY FOR DEV
Collapse Linked work items Linked work items Link a work item
Collapse Linked work items
Collapse Linked work items
Linked work items
Link a work item
Link a work item
clones
clones
JY-20500 is not done
JY-20500
Batch initial sync for Salesforce
Batch initial sync for Salesforce
Backlog - Change status
BACKLOG
Unlink work item
Collapse Activity Activity
Collapse Activity
Collapse Activity
Activity...
|
Firefox
|
[JY-20501] Batch initial sync for Hubspot - Jira — [JY-20501] Batch initial sync for Hubspot - Jira — Work...
|
jiminny.atlassian.net/browse/JY-20501
|
74360
|
|
74361
|
Platform Team - Backlog - Jira
Service-Desk - Queu Platform Team - Backlog - Jira
Service-Desk - Queues - Platform team - Service space - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
Close tab
Feed — jiminny — Sentry
Feed — jiminny — Sentry
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Sidebar
Sidebar
Top Bar
Top Bar
Main Content
Main Content
Expand sidebar [
Expand sidebar [
Switch sites or apps
Switch sites or apps
Go to your Jira homepage
Search, press enter to navigate to advanced search with your text query
Create
Create
Rovo Ask Rovo
Ask Rovo
Notifications
Notifications
Help
Help
Settings
Settings
[EMAIL]
[EMAIL]
Spaces
Spaces
/
Jiminny (New) Jiminny (New)
Jiminny (New)
/
Epic - Change parent
JY-15971
JY-15971
/
Story - Change work type
JY-20501
JY-20501
Copy link
Batch initial sync for Hubspot- Summary, edit
Batch initial sync for Hubspot
Batch initial sync for Hubspot
Add or create work related to this Story
Add or create work related to this Story
View app actions
View app actions
Collapse Description Description
Collapse Description
Collapse Description
Description
Edit Description, edit
Currently synching initial user profile (opportunities) is not working sufficiently when a huge amount of objects are imported from the CRM into Jiminny.
Problems:
Importing deals can take hours
Solution:
The current
syncOpportunities()
should only read the batches of deals from Hubspot and store the payload in Redis
There should be a separate job
import object
per batches of 100 updated deals which reads the info for objects from Redis and import them in Jiminny
There should be retry mechanism of the jobs so that in case they are using spot instance for processing which is turned off, the job will be retried
We should clean the Redis in 24 hours in case there are objects which are still not processed
Collapse Subtasks Subtasks Work item actions Configure columns Create subtask
Collapse Subtasks
Collapse Subtasks
Subtasks
Work item actions
Work item actions
Configure columns
Configure columns
Create subtask
Create subtask
0
% Done
Work
Work
More actions for Work
More actions for Work
Priority
Priority
More actions for Priority
More actions for Priority
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Edit Priority
Medium
Unassigned- edit Assignee
Unassigned
Ready for Dev - Change status
READY FOR DEV
Work
Work
More actions for Work
More actions for Work
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Priority
Priority
More actions for Priority
More actions for Priority
Edit Priority
Medium
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Unassigned- edit Assignee
Unassigned
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
Ready for Dev - Change status
READY FOR DEV
Collapse Linked work items Linked work items Link a work item
Collapse Linked work items
Collapse Linked work items
Linked work items
Link a work item
Link a work item
clones
clones
JY-20500 is not done
JY-20500
Batch initial sync for Salesforce
Batch initial sync for Salesforce
Backlog - Change status
BACKLOG
Unlink work item
Collapse Activity Activity
Collapse Activity
Collapse Activity
Activity
All
All
Comments
Comments
History
History
Work log
Work log
Atlassian Intelligence Summarise
Summarise
Newest first Newest first
Newest first
Add a comment…
Suggest a reply...
Suggest a reply...
Who is working on this...?
Who is working on this...?
Status update...
Status update...
Pro tip:
press
M
to comment
More information about Nikolay Nikolov
More information about Nikolay Nikolov
Nikolay Nikolov
Copy link to comment
20 April 2026 at 14:24
BE 1, QA: 1
Reply
Add thumbs up reaction
Add reaction
Edit
More actions
More information about Nikolay Nikolov
More information about Nikolay Nikolov
Nikolay Nikolov
Copy link to comment
20 April 2026 at 14:07
Initial Owner/Profile Sync for Opportunities
Initial Owner/Profile Sync for Opportunities
Where It Happens
Where It Happens
Trigger:
ProfileCreated
event →
SyncProfileOpportunities
listener
Turn on wrap
Copy as text
1
User connects to CRM → Profile created → ProfileCreated event
2
↓
3
SyncProfileOpportunities::handle()
4
↓
5
SyncOpportunitiesJob dispatched
Location
Location
SyncProfileOpportunities.php
How It Works
How It Works
Step
Action
1
ProfileCreated
event fires when a new CRM profile is created
2
SyncProfileOpportunities
listener handles it
3
Dispatches
SyncOpportunitiesJob
with
crm_profile_id
parameter
4
Uses
LAST_MODIFIED_BY_PROFILE_SYNC_OPPORTUNITY_STRATEGY...
|
Firefox
|
[JY-20501] Batch initial sync for Hubspot - Jira — [JY-20501] Batch initial sync for Hubspot - Jira — Work...
|
jiminny.atlassian.net/browse/JY-20501
|
74361
|
|
74362
|
Platform Team - Backlog - Jira
Service-Desk - Queu Platform Team - Backlog - Jira
Service-Desk - Queues - Platform team - Service space - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
Close tab
Feed — jiminny — Sentry
Feed — jiminny — Sentry
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Sidebar
Sidebar
Top Bar
Top Bar
Main Content
Main Content
Expand sidebar [
Expand sidebar [
Switch sites or apps
Switch sites or apps
Go to your Jira homepage
Search, press enter to navigate to advanced search with your text query
Create
Create
Rovo Ask Rovo
Ask Rovo
Notifications
Notifications
Help
Help
Settings
Settings
[EMAIL]
[EMAIL]
Spaces
Spaces
/
Jiminny (New) Jiminny (New)
Jiminny (New)
/
Epic - Change parent
JY-15971
JY-15971
/
Story - Change work type
JY-20501
JY-20501
Copy link
Batch initial sync for Hubspot- Summary, edit
Batch initial sync for Hubspot
Batch initial sync for Hubspot
Add or create work related to this Story
Add or create work related to this Story
View app actions
View app actions
Collapse Description Description
Collapse Description
Collapse Description
Description
Edit Description, edit
Currently synching initial user profile (opportunities) is not working sufficiently when a huge amount of objects are imported from the CRM into Jiminny.
Problems:
Importing deals can take hours
Solution:
The current
syncOpportunities()
should only read the batches of deals from Hubspot and store the payload in Redis
There should be a separate job
import object
per batches of 100 updated deals which reads the info for objects from Redis and import them in Jiminny
There should be retry mechanism of the jobs so that in case they are using spot instance for processing which is turned off, the job will be retried
We should clean the Redis in 24 hours in case there are objects which are still not processed
Collapse Subtasks Subtasks Work item actions Configure columns Create subtask
Collapse Subtasks
Collapse Subtasks
Subtasks
Work item actions
Work item actions
Configure columns
Configure columns
Create subtask
Create subtask
0
% Done
Work
Work
More actions for Work
More actions for Work
Priority
Priority
More actions for Priority
More actions for Priority
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Edit Priority
Medium
Unassigned- edit Assignee
Unassigned
Ready for Dev - Change status
READY FOR DEV
Work
Work
More actions for Work
More actions for Work
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Priority
Priority
More actions for Priority
More actions for Priority
Edit Priority
Medium
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Unassigned- edit Assignee
Unassigned
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
Ready for Dev - Change status
READY FOR DEV
Collapse Linked work items Linked work items Link a work item
Collapse Linked work items
Collapse Linked work items
Linked work items
Link a work item
Link a work item
clones
clones
JY-20500 is not done
JY-20500
Batch initial sync for Salesforce
Batch initial sync for Salesforce
Backlog - Change status
BACKLOG
Unlink work item
Collapse Activity Activity
Collapse Activity
Collapse Activity
Activity
All
All
Comments
Comments
History
History
Work log
Work log
Atlassian Intelligence Summarise
Summarise
Newest first Newest first
Newest first
Add a comment…
Suggest a reply...
Suggest a reply...
Who is working on this...?
Who is working on this...?
Status update...
Status update...
Pro tip:
press
M
to comment
More information about Nikolay Nikolov
More information about Nikolay Nikolov
Nikolay Nikolov
Copy link to comment
20 April 2026 at 14:24
BE 1, QA: 1
Reply
Add thumbs up reaction
Add reaction
Edit
More actions
More information about Nikolay Nikolov
More information about Nikolay Nikolov
Nikolay Nikolov
Copy link to comment
20 April 2026 at 14:07
Initial Owner/Profile Sync for Opportunities
Initial Owner/Profile Sync for Opportunities
Where It Happens
Where It Happens
Trigger:
ProfileCreated
event →
SyncProfileOpportunities
listener
Turn on wrap
Copy as text
1
User connects to CRM → Profile created → ProfileCreated event
2
↓
3
SyncProfileOpportunities::handle()
4
↓
5
SyncOpportunitiesJob dispatched
Location
Location
SyncProfileOpportunities.php
How It Works
How It Works
Step
Action
1
ProfileCreated
event fires when a new CRM profile is created
2
SyncProfileOpportunities
listener handles it
3
Dispatches
SyncOpportunitiesJob
with
crm_profile_id
parameter
4
Uses
LAST_MODIFIED_BY_PROFILE_SYNC_OPPORTUNITY_STRATEGY...
|
Firefox
|
[JY-20501] Batch initial sync for Hubspot - Jira — [JY-20501] Batch initial sync for Hubspot - Jira — Work...
|
jiminny.atlassian.net/browse/JY-20501
|
74362
|
|
74363
|
Platform Team - Backlog - Jira
Service-Desk - Queu Platform Team - Backlog - Jira
Service-Desk - Queues - Platform team - Service space - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
Close tab
Feed — jiminny — Sentry
Feed — jiminny — Sentry
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Sidebar
Sidebar
Top Bar
Top Bar
Main Content
Main Content
Expand sidebar [
Expand sidebar [
Switch sites or apps
Switch sites or apps
Go to your Jira homepage
Search, press enter to navigate to advanced search with your text query
Create
Create
Rovo Ask Rovo
Ask Rovo
Notifications
Notifications
Help
Help
Settings
Settings
[EMAIL]
[EMAIL]
Spaces
Spaces
/
Jiminny (New) Jiminny (New)
Jiminny (New)
/
Epic - Change parent
JY-15971
JY-15971
/
Story - Change work type
JY-20501
JY-20501
Copy link
Batch initial sync for Hubspot- Summary, edit
Batch initial sync for Hubspot
Batch initial sync for Hubspot
Add or create work related to this Story
Add or create work related to this Story
View app actions
View app actions
Collapse Description Description
Collapse Description
Collapse Description
Description
Edit Description, edit
Currently synching initial user profile (opportunities) is not working sufficiently when a huge amount of objects are imported from the CRM into Jiminny.
Problems:
Importing deals can take hours
Solution:
The current
syncOpportunities()
should only read the batches of deals from Hubspot and store the payload in Redis
There should be a separate job
import object
per batches of 100 updated deals which reads the info for objects from Redis and import them in Jiminny
There should be retry mechanism of the jobs so that in case they are using spot instance for processing which is turned off, the job will be retried
We should clean the Redis in 24 hours in case there are objects which are still not processed
Collapse Subtasks Subtasks Work item actions Configure columns Create subtask
Collapse Subtasks
Collapse Subtasks
Subtasks
Work item actions
Work item actions
Configure columns
Configure columns
Create subtask
Create subtask
0
% Done
Work
Work
More actions for Work
More actions for Work
Priority
Priority
More actions for Priority
More actions for Priority
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Edit Priority
Medium
Unassigned- edit Assignee
Unassigned
Ready for Dev - Change status
READY FOR DEV
Work
Work
More actions for Work
More actions for Work
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Priority
Priority
More actions for Priority
More actions for Priority
Edit Priority
Medium
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Unassigned- edit Assignee
Unassigned
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
Ready for Dev - Change status
READY FOR DEV
Collapse Linked work items Linked work items Link a work item
Collapse Linked work items
Collapse Linked work items
Linked work items
Link a work item
Link a work item
clones
clones
JY-20500 is not done
JY-20500
Batch initial sync for Salesforce
Batch initial sync for Salesforce
Backlog - Change status
BACKLOG
Unlink work item
Collapse Activity Activity
Collapse Activity
Collapse Activity
Activity
All
All
Comments
Comments
History
History
Work log
Work log
Atlassian Intelligence Summarise
Summarise
Newest first Newest first
Newest first
Add a comment…
Suggest a reply...
Suggest a reply...
Who is working on this...?
Who is working on this...?
Status update...
Status update...
Pro tip:
press
M
to comment
More information about Nikolay Nikolov
More information about Nikolay Nikolov
Nikolay Nikolov
Copy link to comment
20 April 2026 at 14:24
BE 1, QA: 1
Reply
Add thumbs up reaction
Add reaction
Edit
More actions
More information about Nikolay Nikolov
More information about Nikolay Nikolov
Nikolay Nikolov
Copy link to comment
20 April 2026 at 14:07
Initial Owner/Profile Sync for Opportunities
Initial Owner/Profile Sync for Opportunities
Where It Happens
Where It Happens
Trigger:
ProfileCreated
event →
SyncProfileOpportunities
listener
Turn on wrap
Copy as text
1
User connects to CRM → Profile created → ProfileCreated event
2
↓
3
SyncProfileOpportunities::handle()
4
↓
5
SyncOpportunitiesJob dispatched
Location
Location
SyncProfileOpportunities.php
How It Works
How It Works
Step
Action
1
ProfileCreated
event fires when a new CRM profile is created
2
SyncProfileOpportunities
listener handles it
3
Dispatches
SyncOpportunitiesJob
with
crm_profile_id
parameter
4
Uses
LAST_MODIFIED_BY_PROFILE_SYNC_OPPORTUNITY_STRATEGY
Step
1
2
3
4
Action
ProfileCreated
event fires when a new CRM profile is created
SyncProfileOpportunities
listener handles it
Dispatches
SyncOpportunitiesJob
with
crm_profile_id
parameter
Uses
LAST_MODIFIED_BY_PROFILE_SYNC_OPPORTUNITY_STRATEGY
Providers Supported (lines 51-61)
Providers Supported (lines 51-61)
HubSpot
Salesforce
Batching?
Batching?
No batching
- Uses
SyncOpportunitiesJob
which calls
syncOpportunities()
:...
|
Firefox
|
[JY-20501] Batch initial sync for Hubspot - Jira — [JY-20501] Batch initial sync for Hubspot - Jira — Work...
|
jiminny.atlassian.net/browse/JY-20501
|
74363
|
|
74364
|
Platform Team - Backlog - Jira
Service-Desk - Queu Platform Team - Backlog - Jira
Service-Desk - Queues - Platform team - Service space - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
Close tab
Feed — jiminny — Sentry
Feed — jiminny — Sentry
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Sidebar
Sidebar
Top Bar
Top Bar
Main Content
Main Content
Expand sidebar [
Expand sidebar [
Switch sites or apps
Switch sites or apps
Go to your Jira homepage
Search, press enter to navigate to advanced search with your text query
Create
Create
Rovo Ask Rovo
Ask Rovo
Notifications
Notifications
Help
Help
Settings
Settings
[EMAIL]
[EMAIL]
Spaces
Spaces
/
Jiminny (New) Jiminny (New)
Jiminny (New)
/
Epic - Change parent
JY-15971
JY-15971
/
Story - Change work type
JY-20501
JY-20501
Copy link
Batch initial sync for Hubspot- Summary, edit
Batch initial sync for Hubspot
Batch initial sync for Hubspot
Add or create work related to this Story
Add or create work related to this Story
View app actions
View app actions
Collapse Description Description
Collapse Description
Collapse Description
Description
Edit Description, edit
Currently synching initial user profile (opportunities) is not working sufficiently when a huge amount of objects are imported from the CRM into Jiminny.
Problems:
Importing deals can take hours
Solution:
The current
syncOpportunities()
should only read the batches of deals from Hubspot and store the payload in Redis
There should be a separate job
import object
per batches of 100 updated deals which reads the info for objects from Redis and import them in Jiminny
There should be retry mechanism of the jobs so that in case they are using spot instance for processing which is turned off, the job will be retried
We should clean the Redis in 24 hours in case there are objects which are still not processed
Collapse Subtasks Subtasks Work item actions Configure columns Create subtask
Collapse Subtasks
Collapse Subtasks
Subtasks
Work item actions
Work item actions
Configure columns
Configure columns
Create subtask
Create subtask
0
% Done
Work
Work
More actions for Work
More actions for Work
Priority
Priority
More actions for Priority
More actions for Priority
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Edit Priority
Medium
Unassigned- edit Assignee
Unassigned
Ready for Dev - Change status
READY FOR DEV
Work
Work
More actions for Work
More actions for Work
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Priority
Priority
More actions for Priority
More actions for Priority
Edit Priority
Medium
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Unassigned- edit Assignee
Unassigned
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
Ready for Dev - Change status
READY FOR DEV
Collapse Linked work items Linked work items Link a work item
Collapse Linked work items
Collapse Linked work items
Linked work items
Link a work item
Link a work item
clones
clones
JY-20500 is not done
JY-20500
Batch initial sync for Salesforce
Batch initial sync for Salesforce
Backlog - Change status
BACKLOG
Unlink work item
Collapse Activity Activity
Collapse Activity
Collapse Activity
Activity
All
All
Comments
Comments
History
History
Work log
Work log
Atlassian Intelligence Summarise
Summarise
Newest first Newest first
Newest first
Add a comment…
Suggest a reply...
Suggest a reply...
Who is working on this...?
Who is working on this...?
Status update...
Status update...
Pro tip:
press
M
to comment
More information about Nikolay Nikolov
More information about Nikolay Nikolov
Nikolay Nikolov
Copy link to comment
20 April 2026 at 14:24
BE 1, QA: 1
Reply
Add thumbs up reaction
Add reaction
Edit
More actions
More information about Nikolay Nikolov
More information about Nikolay Nikolov
Nikolay Nikolov
Copy link to comment
20 April 2026 at 14:07
Initial Owner/Profile Sync for Opportunities
Initial Owner/Profile Sync for Opportunities
Where It Happens
Where It Happens
Trigger:
ProfileCreated
event →
SyncProfileOpportunities
listener
Turn on wrap
Copy as text
1
User connects to CRM → Profile created → ProfileCreated event
2
↓
3
SyncProfileOpportunities::handle()
4
↓
5
SyncOpportunitiesJob dispatched
Location
Location
SyncProfileOpportunities.php
How It Works
How It Works
Step
Action
1
ProfileCreated
event fires when a new CRM profile is created
2
SyncProfileOpportunities
listener handles it
3
Dispatches
SyncOpportunitiesJob
with
crm_profile_id
parameter
4
Uses
LAST_MODIFIED_BY_PROFILE_SYNC_OPPORTUNITY_STRATEGY
Step
1
2
3
4
Action
ProfileCreated
event fires when a new CRM profile is created
SyncProfileOpportunities
listener handles it
Dispatches
SyncOpportunitiesJob
with
crm_profile_id
parameter
Uses
LAST_MODIFIED_BY_PROFILE_SYNC_OPPORTUNITY_STRATEGY
Providers Supported (lines 51-61)
Providers Supported (lines 51-61)
HubSpot
Salesforce
Batching?
Batching?
No batching
- Uses
SyncOpportunitiesJob
which calls
syncOpportunities()
:
Salesforce:
One-by-one (
importOpportunity()
in a loop)
HubSpot:
In-memory buffer of 800, but still processes via
processOpportunityBatch()
Reply
Add thumbs up reaction
Add reaction
Edit
More actions
Resize work item view side panel...
|
Firefox
|
[JY-20501] Batch initial sync for Hubspot - Jira — [JY-20501] Batch initial sync for Hubspot - Jira — Work...
|
jiminny.atlassian.net/browse/JY-20501
|
74364
|
|
74365
|
Platform Team - Backlog - Jira
Service-Desk - Queu Platform Team - Backlog - Jira
Service-Desk - Queues - Platform team - Service space - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
Close tab
Feed — jiminny — Sentry
Feed — jiminny — Sentry
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Sidebar
Sidebar
Top Bar
Top Bar
Main Content
Main Content
Expand sidebar [
Expand sidebar [
Switch sites or apps
Switch sites or apps
Go to your Jira homepage
Search, press enter to navigate to advanced search with your text query
Create
Create
Rovo Ask Rovo
Ask Rovo
Notifications
Notifications
Help
Help
Settings
Settings
[EMAIL]
[EMAIL]
Spaces
Spaces
/
Jiminny (New) Jiminny (New)
Jiminny (New)
/
Epic - Change parent
JY-15971
JY-15971
/
Story - Change work type
JY-20501
JY-20501
Copy link
Batch initial sync for Hubspot- Summary, edit
Batch initial sync for Hubspot
Batch initial sync for Hubspot
Add or create work related to this Story
Add or create work related to this Story
View app actions
View app actions
Collapse Description Description
Collapse Description
Collapse Description
Description
Edit Description, edit
Currently synching initial user profile (opportunities) is not working sufficiently when a huge amount of objects are imported from the CRM into Jiminny.
Problems:
Importing deals can take hours
Solution:
The current
syncOpportunities()
should only read the batches of deals from Hubspot and store the payload in Redis
There should be a separate job
import object
per batches of 100 updated deals which reads the info for objects from Redis and import them in Jiminny
There should be retry mechanism of the jobs so that in case they are using spot instance for processing which is turned off, the job will be retried
We should clean the Redis in 24 hours in case there are objects which are still not processed
Collapse Subtasks Subtasks Work item actions Configure columns Create subtask
Collapse Subtasks
Collapse Subtasks
Subtasks
Work item actions
Work item actions
Configure columns
Configure columns
Create subtask
Create subtask
0
% Done
Work
Work
More actions for Work
More actions for Work
Priority
Priority
More actions for Priority
More actions for Priority
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Edit Priority
Medium
Unassigned- edit Assignee
Unassigned
Ready for Dev - Change status
READY FOR DEV
Work
Work
More actions for Work
More actions for Work
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Priority
Priority
More actions for Priority
More actions for Priority
Edit Priority
Medium
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Unassigned- edit Assignee
Unassigned
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
Ready for Dev - Change status
READY FOR DEV
Collapse Linked work items Linked work items Link a work item
Collapse Linked work items
Collapse Linked work items
Linked work items
Link a work item
Link a work item
clones
clones
JY-20500 is not done
JY-20500
Batch initial sync for Salesforce
Batch initial sync for Salesforce
Backlog - Change status
BACKLOG
Unlink work item
Collapse Activity Activity
Collapse Activity
Collapse Activity
Activity
All
All
Comments
Comments
History
History
Work log
Work log
Atlassian Intelligence Summarise
Summarise
Newest first Newest first
Newest first
Add a comment…
Suggest a reply...
Suggest a reply...
Who is working on this...?
Who is working on this...?
Status update...
Status update...
Pro tip:
press
M
to comment
More information about Nikolay Nikolov
More information about Nikolay Nikolov
Nikolay Nikolov
Copy link to comment
20 April 2026 at 14:24
BE 1, QA: 1
Reply
Add thumbs up reaction
Add reaction
Edit
More actions
More information about Nikolay Nikolov
More information about Nikolay Nikolov
Nikolay Nikolov
Copy link to comment...
|
Firefox
|
[JY-20501] Batch initial sync for Hubspot - Jira — [JY-20501] Batch initial sync for Hubspot - Jira — Work...
|
jiminny.atlassian.net/browse/JY-20501
|
74365
|
|
74366
|
Platform Team - Backlog - Jira
Service-Desk - Queu Platform Team - Backlog - Jira
Service-Desk - Queues - Platform team - Service space - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
Close tab
Feed — jiminny — Sentry
Feed — jiminny — Sentry
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Sidebar
Sidebar
Top Bar
Top Bar
Main Content
Main Content
Expand sidebar [
Expand sidebar [
Switch sites or apps
Switch sites or apps
Go to your Jira homepage
Search, press enter to navigate to advanced search with your text query
Create
Create
Rovo Ask Rovo
Ask Rovo
Notifications
Notifications
Help
Help
Settings
Settings
[EMAIL]
[EMAIL]
Spaces
Spaces
/
Jiminny (New) Jiminny (New)
Jiminny (New)
/
Epic - Change parent
JY-15971
JY-15971
/
Story - Change work type
JY-20501
JY-20501
Copy link
Batch initial sync for Hubspot- Summary, edit
Batch initial sync for Hubspot
Batch initial sync for Hubspot
Add or create work related to this Story
Add or create work related to this Story
View app actions
View app actions
Collapse Description Description
Collapse Description
Collapse Description
Description
Edit Description, edit
Currently synching initial user profile (opportunities) is not working sufficiently when a huge amount of objects are imported from the CRM into Jiminny.
Problems:
Importing deals can take hours
Solution:
The current
syncOpportunities()
should only read the batches of deals from Hubspot and store the payload in Redis
There should be a separate job
import object
per batches of 100 updated deals which reads the info for objects from Redis and import them in Jiminny
There should be retry mechanism of the jobs so that in case they are using spot instance for processing which is turned off, the job will be retried
We should clean the Redis in 24 hours in case there are objects which are still not processed
Collapse Subtasks Subtasks Work item actions Configure columns Create subtask
Collapse Subtasks
Collapse Subtasks
Subtasks
Work item actions
Work item actions
Configure columns
Configure columns
Create subtask
Create subtask
0
% Done
Work
Work
More actions for Work
More actions for Work
Priority
Priority
More actions for Priority
More actions for Priority
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Edit Priority
Medium
Unassigned- edit Assignee
Unassigned
Ready for Dev - Change status
READY FOR DEV
Work
Work
More actions for Work
More actions for Work
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Priority
Priority
More actions for Priority
More actions for Priority
Edit Priority
Medium
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Unassigned- edit Assignee
Unassigned
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
Ready for Dev - Change status
READY FOR DEV
Collapse Linked work items Linked work items Link a work item
Collapse Linked work items
Collapse Linked work items
Linked work items
Link a work item
Link a work item
clones
clones
JY-20500 is not done
JY-20500
Batch initial sync for Salesforce
Batch initial sync for Salesforce
Backlog - Change status
BACKLOG
Unlink work item
Collapse Activity Activity
Collapse Activity
Collapse Activity
Activity
All
All
Comments
Comments
History
History
Work log
Work log
Atlassian Intelligence Summarise
Summarise
Newest first Newest first
Newest first
Add a comment…
Suggest a reply...
Suggest a reply...
Who is working on this...?
Who is working on this...?
Status update...
Status update...
Pro tip:
press
M
to comment
More information about Nikolay Nikolov
More information about Nikolay Nikolov
Nikolay Nikolov
Copy link to comment
20 April 2026 at 14:24
BE 1, QA: 1
Reply
Add thumbs up reaction
Add reaction
Edit
More actions
More information about Nikolay Nikolov
More information about Nikolay Nikolov
Nikolay Nikolov
Copy link to comment
20 April 2026 at 14:07
Initial Owner/Profile Sync for Opportunities
Initial Owner/Profile Sync for Opportunities...
|
Firefox
|
[JY-20501] Batch initial sync for Hubspot - Jira — [JY-20501] Batch initial sync for Hubspot - Jira — Work...
|
jiminny.atlassian.net/browse/JY-20501
|
74366
|
|
74367
|
Platform Team - Backlog - Jira
Service-Desk - Queu Platform Team - Backlog - Jira
Service-Desk - Queues - Platform team - Service space - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
Close tab
Feed — jiminny — Sentry
Feed — jiminny — Sentry
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Sidebar
Sidebar
Top Bar
Top Bar
Main Content
Main Content
Expand sidebar [
Expand sidebar [
Switch sites or apps
Switch sites or apps
Go to your Jira homepage
Search, press enter to navigate to advanced search with your text query
Create
Create
Rovo Ask Rovo
Ask Rovo
Notifications
Notifications
Help
Help
Settings
Settings
[EMAIL]
[EMAIL]
Spaces
Spaces
/
Jiminny (New) Jiminny (New)
Jiminny (New)
/
Epic - Change parent
JY-15971
JY-15971
/
Story - Change work type
JY-20501
JY-20501
Copy link
Batch initial sync for Hubspot- Summary, edit
Batch initial sync for Hubspot
Batch initial sync for Hubspot
Add or create work related to this Story
Add or create work related to this Story
View app actions
View app actions
Collapse Description Description
Collapse Description
Collapse Description
Description
Edit Description, edit
Currently synching initial user profile (opportunities) is not working sufficiently when a huge amount of objects are imported from the CRM into Jiminny.
Problems:
Importing deals can take hours
Solution:
The current
syncOpportunities()
should only read the batches of deals from Hubspot and store the payload in Redis
There should be a separate job
import object
per batches of 100 updated deals which reads the info for objects from Redis and import them in Jiminny
There should be retry mechanism of the jobs so that in case they are using spot instance for processing which is turned off, the job will be retried
We should clean the Redis in 24 hours in case there are objects which are still not processed
Collapse Subtasks Subtasks Work item actions Configure columns Create subtask
Collapse Subtasks
Collapse Subtasks
Subtasks
Work item actions
Work item actions
Configure columns
Configure columns
Create subtask
Create subtask
0
% Done
Work
Work
More actions for Work
More actions for Work
Priority
Priority
More actions for Priority
More actions for Priority
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Edit Priority
Medium
Unassigned- edit Assignee
Unassigned
Ready for Dev - Change status
READY FOR DEV
Work
Work
More actions for Work
More actions for Work
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Priority
Priority
More actions for Priority
More actions for Priority
Edit Priority
Medium
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Unassigned- edit Assignee
Unassigned
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
Ready for Dev - Change status
READY FOR DEV
Collapse Linked work items Linked work items Link a work item
Collapse Linked work items
Collapse Linked work items
Linked work items
Link a work item
Link a work item
clones
clones
JY-20500 is not done
JY-20500
Batch initial sync for Salesforce
Batch initial sync for Salesforce
Backlog - Change status
BACKLOG
Unlink work item
Collapse Activity Activity
Collapse Activity
Collapse Activity
Activity
All
All
Comments
Comments
History
History
Work log
Work log
Atlassian Intelligence Summarise
Summarise
Newest first Newest first
Newest first
Add a comment…
Suggest a reply...
Suggest a reply...
Who is working on this...?
Who is working on this...?
Status update...
Status update...
Pro tip:
press
M
to comment
More information about Nikolay Nikolov
More information about Nikolay Nikolov
Nikolay Nikolov
Copy link to comment
20 April 2026 at 14:24
BE 1, QA: 1
Reply
Add thumbs up reaction
Add reaction
Edit
More actions
More information about Nikolay Nikolov
More information about Nikolay Nikolov
Nikolay Nikolov
Copy link to comment
20 April 2026 at 14:07
Initial Owner/Profile Sync for Opportunities
Initial Owner/Profile Sync for Opportunities
Where It Happens
Where It Happens
Trigger:
ProfileCreated
event →
SyncProfileOpportunities
listener
Turn on wrap
Copy as text
1
User connects to CRM → Profile created → ProfileCreated event
2
↓
3
SyncProfileOpportunities::handle()
4
↓
5
SyncOpportunitiesJob dispatched
Location
Location
SyncProfileOpportunities.php
How It Works
How It Works
Step
Action
1
ProfileCreated
event fires when a new CRM profile is created
2
SyncProfileOpportunities
listener handles it
3
Dispatches
SyncOpportunitiesJob
with
crm_profile_id
parameter
4
Uses
LAST_MODIFIED_BY_PROFILE_SYNC_OPPORTUNITY_STRATEGY
Step
1
2
3
4
Action
ProfileCreated
event fires when a new CRM profile is created
SyncProfileOpportunities
listener handles it
Dispatches
SyncOpportunitiesJob
with
crm_profile_id
parameter
Uses
LAST_MODIFIED_BY_PROFILE_SYNC_OPPORTUNITY_STRATEGY
Providers Supported (lines 51-61)
Providers Supported (lines 51-61)
HubSpot
Salesforce
Batching?
Batching?
No batching
- Uses
SyncOpportunitiesJob
which calls
syncOpportunities()...
|
Firefox
|
[JY-20501] Batch initial sync for Hubspot - Jira — [JY-20501] Batch initial sync for Hubspot - Jira — Work...
|
jiminny.atlassian.net/browse/JY-20501
|
74367
|
|
74368
|
Platform Team - Backlog - Jira
Service-Desk - Queu Platform Team - Backlog - Jira
Service-Desk - Queues - Platform team - Service space - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
Close tab
Feed — jiminny — Sentry
Feed — jiminny — Sentry
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Sidebar
Sidebar
Top Bar
Top Bar
Main Content
Main Content
Expand sidebar [
Expand sidebar [
Switch sites or apps
Switch sites or apps
Go to your Jira homepage
Search, press enter to navigate to advanced search with your text query
Create
Create
Rovo Ask Rovo
Ask Rovo
Notifications
Notifications
Help
Help
Settings
Settings
[EMAIL]
[EMAIL]
Spaces
Spaces
/
Jiminny (New) Jiminny (New)
Jiminny (New)
/
Epic - Change parent
JY-15971
JY-15971
/
Story - Change work type
JY-20501
JY-20501
Copy link
Batch initial sync for Hubspot- Summary, edit
Batch initial sync for Hubspot
Batch initial sync for Hubspot
Add or create work related to this Story
Add or create work related to this Story
View app actions
View app actions
Collapse Description Description
Collapse Description
Collapse Description
Description
Edit Description, edit
Currently synching initial user profile (opportunities) is not working sufficiently when a huge amount of objects are imported from the CRM into Jiminny.
Problems:
Importing deals can take hours
Solution:
The current
syncOpportunities()
should only read the batches of deals from Hubspot and store the payload in Redis
There should be a separate job
import object
per batches of 100 updated deals which reads the info for objects from Redis and import them in Jiminny
There should be retry mechanism of the jobs so that in case they are using spot instance for processing which is turned off, the job will be retried
We should clean the Redis in 24 hours in case there are objects which are still not processed
Collapse Subtasks Subtasks Work item actions Configure columns Create subtask
Collapse Subtasks
Collapse Subtasks
Subtasks
Work item actions
Work item actions
Configure columns
Configure columns
Create subtask
Create subtask
0
% Done
Work
Work
More actions for Work
More actions for Work
Priority
Priority
More actions for Priority
More actions for Priority
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Edit Priority
Medium
Unassigned- edit Assignee
Unassigned
Ready for Dev - Change status
READY FOR DEV
Work
Work
More actions for Work
More actions for Work
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Priority
Priority
More actions for Priority
More actions for Priority
Edit Priority
Medium
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Unassigned- edit Assignee
Unassigned
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
Ready for Dev - Change status
READY FOR DEV
Collapse Linked work items Linked work items Link a work item
Collapse Linked work items
Collapse Linked work items
Linked work items
Link a work item
Link a work item
clones
clones
JY-20500 is not done
JY-20500
Batch initial sync for Salesforce
Batch initial sync for Salesforce
Backlog - Change status
BACKLOG
Unlink work item
Collapse Activity Activity
Collapse Activity
Collapse Activity
Activity
All
All
Comments
Comments
History
History
Work log
Work log
Atlassian Intelligence Summarise
Summarise
Newest first Newest first
Newest first
Add a comment…
Suggest a reply...
Suggest a reply...
Who is working on this...?
Who is working on this...?
Status update...
Status update...
Pro tip:
press
M
to comment
More information about Nikolay Nikolov
More information about Nikolay Nikolov
Nikolay Nikolov
Copy link to comment
20 April 2026 at 14:24
BE 1, QA: 1
Reply
Add thumbs up reaction
Add reaction
Edit
More actions
More information about Nikolay Nikolov
More information about Nikolay Nikolov
Nikolay Nikolov
Copy link to comment
20 April 2026 at 14:07
Initial Owner/Profile Sync for Opportunities
Initial Owner/Profile Sync for Opportunities
Where It Happens
Where It Happens
Trigger:
ProfileCreated
event →
SyncProfileOpportunities
listener
Turn on wrap
Copy as text
1
User connects to CRM → Profile created → ProfileCreated event
2
↓
3
SyncProfileOpportunities::handle()
4
↓
5
SyncOpportunitiesJob dispatched
Location
Location
SyncProfileOpportunities.php
How It Works
How It Works
Step
Action
1
ProfileCreated
event fires when a new CRM profile is created
2
SyncProfileOpportunities
listener handles it
3
Dispatches
SyncOpportunitiesJob
with
crm_profile_id
parameter
4
Uses
LAST_MODIFIED_BY_PROFILE_SYNC_OPPORTUNITY_STRATEGY
Step
1
2
3
4
Action
ProfileCreated
event fires when a new CRM profile is created
SyncProfileOpportunities
listener handles it
Dispatches
SyncOpportunitiesJob
with
crm_profile_id
parameter
Uses
LAST_MODIFIED_BY_PROFILE_SYNC_OPPORTUNITY_STRATEGY
Providers Supported (lines 51-61)
Providers Supported (lines 51-61)
HubSpot
Salesforce
Batching?
Batching?
No batching
- Uses
SyncOpportunitiesJob
which calls
syncOpportunities()
:
Salesforce:
One-by-one (
importOpportunity()
in a loop)
HubSpot:
In-memory buffer of 800, but still processes via
processOpportunityBatch()
Reply
Add thumbs up reaction
Add reaction
Edit
More actions
Resize work item view side panel
Watch options: You are not watching this issue, 2 people watching...
|
Firefox
|
[JY-20501] Batch initial sync for Hubspot - Jira — [JY-20501] Batch initial sync for Hubspot - Jira — Work...
|
jiminny.atlassian.net/browse/JY-20501
|
74368
|
|
74369
|
Platform Team - Backlog - Jira
Service-Desk - Queu Platform Team - Backlog - Jira
Service-Desk - Queues - Platform team - Service space - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
Close tab
Feed — jiminny — Sentry
Feed — jiminny — Sentry
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Sidebar
Sidebar
Top Bar
Top Bar
Main Content
Main Content
Expand sidebar [
Expand sidebar [
Switch sites or apps
Switch sites or apps
Go to your Jira homepage
Search, press enter to navigate to advanced search with your text query
Create
Create
Rovo Ask Rovo
Ask Rovo
Notifications
Notifications
Help
Help
Settings
Settings
[EMAIL]
[EMAIL]
Spaces
Spaces
/
Jiminny (New) Jiminny (New)
Jiminny (New)
/
Epic - Change parent
JY-15971
JY-15971
/
Story - Change work type
JY-20501
JY-20501
Copy link
Batch initial sync for Hubspot- Summary, edit
Batch initial sync for Hubspot
Batch initial sync for Hubspot
Add or create work related to this Story
Add or create work related to this Story
View app actions
View app actions
Collapse Description Description
Collapse Description
Collapse Description
Description
Edit Description, edit
Currently synching initial user profile (opportunities) is not working sufficiently when a huge amount of objects are imported from the CRM into Jiminny.
Problems:
Importing deals can take hours
Solution:
The current
syncOpportunities()
should only read the batches of deals from Hubspot and store the payload in Redis
There should be a separate job
import object
per batches of 100 updated deals which reads the info for objects from Redis and import them in Jiminny
There should be retry mechanism of the jobs so that in case they are using spot instance for processing which is turned off, the job will be retried
We should clean the Redis in 24 hours in case there are objects which are still not processed
Collapse Subtasks Subtasks Work item actions Configure columns Create subtask
Collapse Subtasks
Collapse Subtasks
Subtasks
Work item actions
Work item actions
Configure columns
Configure columns
Create subtask
Create subtask
0
% Done
Work
Work
More actions for Work
More actions for Work
Priority
Priority
More actions for Priority
More actions for Priority
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Edit Priority
Medium
Unassigned- edit Assignee
Unassigned
Ready for Dev - Change status
READY FOR DEV
Work
Work
More actions for Work
More actions for Work
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Priority
Priority
More actions for Priority
More actions for Priority
Edit Priority
Medium
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Unassigned- edit Assignee
Unassigned
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
Ready for Dev - Change status
READY FOR DEV
Collapse Linked work items Linked work items Link a work item
Collapse Linked work items
Collapse Linked work items
Linked work items
Link a work item
Link a work item
clones
clones
JY-20500 is not done
JY-20500
Batch initial sync for Salesforce
Batch initial sync for Salesforce
Backlog - Change status
BACKLOG
Unlink work item
Collapse Activity Activity
Collapse Activity
Collapse Activity
Activity
All
All
Comments
Comments
History
History
Work log
Work log
Atlassian Intelligence Summarise
Summarise
Newest first Newest first
Newest first
Add a comment…
Suggest a reply...
Suggest a reply...
Who is working on this...?
Who is working on this...?
Status update...
Status update...
Pro tip:
press
M
to comment
More information about Nikolay Nikolov
More information about Nikolay Nikolov
Nikolay Nikolov
Copy link to comment
20 April 2026 at 14:24
BE 1, QA: 1
Reply
Add thumbs up reaction
Add reaction
Edit
More actions
More information about Nikolay Nikolov
More information about Nikolay Nikolov
Nikolay Nikolov
Copy link to comment
20 April 2026 at 14:07
Initial Owner/Profile Sync for Opportunities
Initial Owner/Profile Sync for Opportunities
Where It Happens
Where It Happens
Trigger:
ProfileCreated
event →
SyncProfileOpportunities
listener
Turn on wrap
Copy as text
1
User connects to CRM → Profile created → ProfileCreated event
2
↓
3
SyncProfileOpportunities::handle()
4
↓
5
SyncOpportunitiesJob dispatched
Location
Location
SyncProfileOpportunities.php
How It Works
How It Works
Step
Action
1
ProfileCreated
event fires when a new CRM profile is created
2
SyncProfileOpportunities
listener handles it
3
Dispatches
SyncOpportunitiesJob
with
crm_profile_id
parameter
4
Uses
LAST_MODIFIED_BY_PROFILE_SYNC_OPPORTUNITY_STRATEGY
Step
1
2
3
4
Action
ProfileCreated
event fires when a new CRM profile is created
SyncProfileOpportunities
listener handles it
Dispatches
SyncOpportunitiesJob
with
crm_profile_id
parameter
Uses
LAST_MODIFIED_BY_PROFILE_SYNC_OPPORTUNITY_STRATEGY
Providers Supported (lines 51-61)
Providers Supported (lines 51-61)
HubSpot
Salesforce
Batching?
Batching?
No batching
- Uses
SyncOpportunitiesJob
which calls
syncOpportunities()
:...
|
Firefox
|
[JY-20501] Batch initial sync for Hubspot - Jira — [JY-20501] Batch initial sync for Hubspot - Jira — Work...
|
jiminny.atlassian.net/browse/JY-20501
|
74369
|
|
74370
|
Platform Team - Backlog - Jira
Service-Desk - Queu Platform Team - Backlog - Jira
Service-Desk - Queues - Platform team - Service space - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
Close tab
Feed — jiminny — Sentry
Feed — jiminny — Sentry
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Sidebar
Sidebar
Top Bar
Top Bar
Main Content
Main Content
Expand sidebar [
Expand sidebar [
Switch sites or apps
Switch sites or apps
Go to your Jira homepage
Search, press enter to navigate to advanced search with your text query
Create
Create
Rovo Ask Rovo
Ask Rovo
Notifications
Notifications
Help
Help
Settings
Settings
[EMAIL]
[EMAIL]
Spaces
Spaces
/
Jiminny (New) Jiminny (New)
Jiminny (New)
/
Epic - Change parent
JY-15971
JY-15971
/
Story - Change work type
JY-20501
JY-20501
Copy link
Batch initial sync for Hubspot- Summary, edit
Batch initial sync for Hubspot
Batch initial sync for Hubspot
Add or create work related to this Story
Add or create work related to this Story
View app actions
View app actions
Collapse Description Description
Collapse Description
Collapse Description
Description
Edit Description, edit
Currently synching initial user profile (opportunities) is not working sufficiently when a huge amount of objects are imported from the CRM into Jiminny.
Problems:
Importing deals can take hours
Solution:
The current
syncOpportunities()
should only read the batches of deals from Hubspot and store the payload in Redis
There should be a separate job
import object
per batches of 100 updated deals which reads the info for objects from Redis and import them in Jiminny
There should be retry mechanism of the jobs so that in case they are using spot instance for processing which is turned off, the job will be retried
We should clean the Redis in 24 hours in case there are objects which are still not processed
Collapse Subtasks Subtasks Work item actions Configure columns Create subtask
Collapse Subtasks
Collapse Subtasks
Subtasks
Work item actions
Work item actions
Configure columns
Configure columns
Create subtask
Create subtask
0
% Done
Work
Work
More actions for Work
More actions for Work
Priority
Priority
More actions for Priority
More actions for Priority
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Edit Priority
Medium
Unassigned- edit Assignee
Unassigned
Ready for Dev - Change status
READY FOR DEV
Work
Work
More actions for Work
More actions for Work
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Priority
Priority
More actions for Priority
More actions for Priority
Edit Priority
Medium
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Unassigned- edit Assignee
Unassigned
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
Ready for Dev - Change status
READY FOR DEV
Collapse Linked work items Linked work items Link a work item
Collapse Linked work items
Collapse Linked work items
Linked work items
Link a work item
Link a work item
clones
clones
JY-20500 is not done
JY-20500
Batch initial sync for Salesforce
Batch initial sync for Salesforce
Backlog - Change status
BACKLOG
Unlink work item
Collapse Activity Activity
Collapse Activity
Collapse Activity
Activity
All
All
Comments
Comments
History
History
Work log
Work log
Atlassian Intelligence Summarise
Summarise
Newest first Newest first
Newest first
Add a comment…
Suggest a reply...
Suggest a reply...
Who is working on this...?
Who is working on this...?
Status update...
Status update...
Pro tip:
press
M
to comment
More information about Nikolay Nikolov
More information about Nikolay Nikolov
Nikolay Nikolov
Copy link to comment
20 April 2026 at 14:24
BE 1, QA: 1
Reply
Add thumbs up reaction
Add reaction
Edit
More actions
More information about Nikolay Nikolov
More information about Nikolay Nikolov
Nikolay Nikolov
Copy link to comment
20 April 2026 at 14:07
Initial Owner/Profile Sync for Opportunities
Initial Owner/Profile Sync for Opportunities
Where It Happens
Where It Happens
Trigger:
ProfileCreated
event →
SyncProfileOpportunities
listener
Turn on wrap
Copy as text
1
User connects to CRM → Profile created → ProfileCreated event
2
↓
3
SyncProfileOpportunities::handle()
4
↓
5
SyncOpportunitiesJob dispatched
Location
Location
SyncProfileOpportunities.php
How It Works
How It Works
Step
Action
1
ProfileCreated
event fires when a new CRM profile is created
2...
|
Firefox
|
[JY-20501] Batch initial sync for Hubspot - Jira — [JY-20501] Batch initial sync for Hubspot - Jira — Work...
|
jiminny.atlassian.net/browse/JY-20501
|
74370
|
|
74371
|
Platform Team - Backlog - Jira
Service-Desk - Queu Platform Team - Backlog - Jira
Service-Desk - Queues - Platform team - Service space - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
Close tab
Feed — jiminny — Sentry
Feed — jiminny — Sentry
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Sidebar
Sidebar
Top Bar
Top Bar
Main Content
Main Content
Expand sidebar [
Expand sidebar [
Switch sites or apps
Switch sites or apps
Go to your Jira homepage
Search, press enter to navigate to advanced search with your text query
Create
Create
Rovo Ask Rovo
Ask Rovo
Notifications
Notifications
Help
Help
Settings
Settings
[EMAIL]
[EMAIL]
Spaces
Spaces
/
Jiminny (New) Jiminny (New)
Jiminny (New)
/
Epic - Change parent
JY-15971
JY-15971
/
Story - Change work type
JY-20501
JY-20501
Copy link
Batch initial sync for Hubspot- Summary, edit
Batch initial sync for Hubspot
Batch initial sync for Hubspot
Add or create work related to this Story
Add or create work related to this Story
View app actions
View app actions
Collapse Description Description
Collapse Description
Collapse Description
Description
Edit Description, edit
Currently synching initial user profile (opportunities) is not working sufficiently when a huge amount of objects are imported from the CRM into Jiminny.
Problems:
Importing deals can take hours
Solution:
The current
syncOpportunities()
should only read the batches of deals from Hubspot and store the payload in Redis
There should be a separate job
import object
per batches of 100 updated deals which reads the info for objects from Redis and import them in Jiminny
There should be retry mechanism of the jobs so that in case they are using spot instance for processing which is turned off, the job will be retried
We should clean the Redis in 24 hours in case there are objects which are still not processed
Collapse Subtasks Subtasks Work item actions Configure columns Create subtask
Collapse Subtasks
Collapse Subtasks
Subtasks
Work item actions
Work item actions
Configure columns
Configure columns
Create subtask
Create subtask
0
% Done
Work
Work
More actions for Work
More actions for Work
Priority
Priority
More actions for Priority
More actions for Priority
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Edit Priority
Medium
Unassigned- edit Assignee
Unassigned
Ready for Dev - Change status
READY FOR DEV
Work
Work
More actions for Work
More actions for Work
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Priority
Priority
More actions for Priority
More actions for Priority
Edit Priority
Medium
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Unassigned- edit Assignee
Unassigned
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
Ready for Dev - Change status
READY FOR DEV
Collapse Linked work items Linked work items Link a work item
Collapse Linked work items
Collapse Linked work items
Linked work items
Link a work item
Link a work item
clones
clones
JY-20500 is not done
JY-20500
Batch initial sync for Salesforce
Batch initial sync for Salesforce
Backlog - Change status
BACKLOG
Unlink work item
Collapse Activity Activity
Collapse Activity
Collapse Activity
Activity
All
All
Comments
Comments
History
History
Work log...
|
Firefox
|
[JY-20501] Batch initial sync for Hubspot - Jira — [JY-20501] Batch initial sync for Hubspot - Jira — Work...
|
jiminny.atlassian.net/browse/JY-20501
|
74371
|
|
74391
|
Platform Team - Backlog - Jira
Service-Desk - Queu Platform Team - Backlog - Jira
Service-Desk - Queues - Platform team - Service space - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
Close tab
Feed — jiminny — Sentry
Feed — jiminny — Sentry
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
Lukas Kovalik - Time Off
Lukas Kovalik - Time Off
Close tab
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Home
Home
My Info
My Info
People
People
Lukas
Collapse Menu
Logo
Search...
Clear Search
Inbox Header Button
Ask chat icon Ask
Ask
Lukas Kovalik
Lukas Kovalik
Senior Developer 2
Senior Developer 2
Job
Job
Personal
Personal
Time Off
Time Off
Emergency
Emergency
Documents
Documents
Training
Training
Benefits
Benefits
Performance
Performance
Edit profile photo
Vitals
Vitals
[PHONE]
[EMAIL]
[EMAIL]
Sofia
Senior Developer 2
Full-Time
Engineering
Dialers & CRM
85
Hire Date
Hire Date
Nov 1, 2021
4y - 6m - 26d
Manager
Manager
Stefka Stoyanova
Stefka Stoyanova
VP Engineering
View in org chart
View in org chart
Time Off
Time Off
26 Days
26
Days
PTO Available
(6 days scheduled)
Request Time Off
Calculate Balance
0 Days
0
Days
Sick Leave Used (YTD)
Request Time Off
0 Days
0
Days
Parental Leave Used (YTD)
Request Time Off
Upcoming Time Off
Upcoming Time Off
May 27
0.5 days of PTO
Edit
Edit
Jun 26 – Jul 5
6 days of PTO
Edit
Edit
History
History
PTO
PTO
All
All
Balance History
Balance History
Time Off Balance History
Date
Sort table by Date
Description
Used Days (-)
Earned Days (+)
Balance
Actions
Actions
01/11/2021...
|
Firefox
|
[JY-20501] Batch initial sync for Hubspot - Jira — [JY-20501] Batch initial sync for Hubspot - Jira — Work...
|
jiminny.atlassian.net/browse/JY-20501
|
74391
|
|
74392
|
Platform Team - Backlog - Jira
Service-Desk - Queu Platform Team - Backlog - Jira
Service-Desk - Queues - Platform team - Service space - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
Close tab
Feed — jiminny — Sentry
Feed — jiminny — Sentry
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
Lukas Kovalik - Time Off
Lukas Kovalik - Time Off
Close tab
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Home
Home
My Info
My Info
People
People
Lukas
Collapse Menu
Logo
Search...
Clear Search
Inbox Header Button
Ask chat icon Ask
Ask
Lukas Kovalik
Lukas Kovalik
Senior Developer 2
Senior Developer 2
Job
Job
Personal
Personal
Time Off
Time Off
Emergency
Emergency
Documents
Documents
Training
Training
Benefits
Benefits
Performance
Performance
Edit profile photo
Vitals
Vitals
[PHONE]
[EMAIL]
[EMAIL]
Sofia
Senior Developer 2
Full-Time
Engineering
Dialers & CRM
85
Hire Date
Hire Date
Nov 1, 2021
4y - 6m - 26d
Manager
Manager
Stefka Stoyanova
Stefka Stoyanova
VP Engineering
View in org chart
View in org chart
Time Off
Time Off
26 Days
26
Days
PTO Available
(6 days scheduled)
Request Time Off
Calculate Balance
0 Days
0
Days
Sick Leave Used (YTD)
Request Time Off
0 Days
0
Days
Parental Leave Used (YTD)
Request Time Off
Upcoming Time Off
Upcoming Time Off
May 27
0.5 days of PTO
Edit
Edit
Jun 26 – Jul 5
6 days of PTO
Edit
Edit
History
History
PTO
PTO
All
All
Balance History
Balance History
Time Off Balance History
Date
Sort table by Date
Description
Used Days (-)
Earned Days (+)
Balance
Actions
Actions
01/11/2021
Moved to a new policy
PTO Accrual Policy was set to a new policy
01/11/2021
You're now eligible to begin accruing time
0.00
01/11/2021
Accrual for 01/11/2021 to 31/12/2021
4.18
4.18
29/12/2021
Time off used for 29/12/2021 to 31/12/2021
-3.00
1.18
01/01/2022
Accrual for 01/01/2022 to 31/12/2022
23.82
25.00
10/01/2022
Balance adjusted
by Mira Lenkova: Unused days PTO from 2021 added.
1.18
26.18
18/04/2022
Time off used for 18/04/2022 to 21/04/2022
-4.00
22.18
04/07/2022
Time off used for 04/07/2022 to 08/07/2022...
|
Firefox
|
[JY-20501] Batch initial sync for Hubspot - Jira — [JY-20501] Batch initial sync for Hubspot - Jira — Work...
|
jiminny.atlassian.net/browse/JY-20501
|
74392
|
|
74393
|
Platform Team - Backlog - Jira
Service-Desk - Queu Platform Team - Backlog - Jira
Service-Desk - Queues - Platform team - Service space - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
Close tab
Feed — jiminny — Sentry
Feed — jiminny — Sentry
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
Lukas Kovalik - Time Off
Lukas Kovalik - Time Off
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Sidebar
Sidebar
Top Bar
Top Bar
Main Content
Main Content
Expand sidebar [
Expand sidebar [
Switch sites or apps
Switch sites or apps
Go to your Jira homepage
Search, press enter to navigate to advanced search with your text query
Create
Create
Rovo Ask Rovo
Ask Rovo
Notifications
Notifications
Help
Help
Settings
Settings
[EMAIL]
[EMAIL]
Spaces
Spaces
/
Jiminny (New) Jiminny (New)
Jiminny (New)
/
Epic - Change parent
JY-15971
JY-15971
/
Story - Change work type
JY-20501
JY-20501
Copy link
Batch initial sync for Hubspot- Summary, edit
Batch initial sync for Hubspot
Batch initial sync for Hubspot
Add or create work related to this Story
Add or create work related to this Story
View app actions
View app actions
Collapse Description Description
Collapse Description
Collapse Description
Description
Edit Description, edit
Currently synching initial user profile (opportunities) is not working sufficiently when a huge amount of objects are imported from the CRM into Jiminny.
Problems:
Importing deals can take hours
Solution:
The current
syncOpportunities()
should only read the batches of deals from Hubspot and store the payload in Redis
There should be a separate job
import object
per batches of 100 updated deals which reads the info for objects from Redis and import them in Jiminny
There should be retry mechanism of the jobs so that in case they are using spot instance for processing which is turned off, the job will be retried
We should clean the Redis in 24 hours in case there are objects which are still not processed
Collapse Subtasks Subtasks Work item actions Configure columns Create subtask
Collapse Subtasks
Collapse Subtasks
Subtasks
Work item actions
Work item actions
Configure columns
Configure columns
Create subtask
Create subtask
0
% Done
Work
Work
More actions for Work
More actions for Work
Priority
Priority
More actions for Priority
More actions for Priority
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Edit Priority
Medium
Unassigned- edit Assignee
Unassigned
Ready for Dev - Change status
READY FOR DEV
Work
Work
More actions for Work
More actions for Work
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Priority
Priority
More actions for Priority
More actions for Priority
Edit Priority
Medium
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Unassigned- edit Assignee
Unassigned
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
Ready for Dev - Change status
READY FOR DEV
Collapse Linked work items Linked work items Link a work item
Collapse Linked work items
Collapse Linked work items
Linked work items
Link a work item
Link a work item
clones
clones
JY-20500 is not done
JY-20500
Batch initial sync for Salesforce
Batch initial sync for Salesforce
Backlog - Change status
BACKLOG
Unlink work item
Collapse Activity Activity
Collapse Activity
Collapse Activity
Activity
All
All
Comments
Comments
History
History
Work log
Work log
Atlassian Intelligence Summarise
Summarise
Newest first Newest first
Newest first
Add a comment…
Suggest a reply...
Suggest a reply...
Who is working on this...?
Who is working on this...?
Status update...
Status update...
Pro tip:
press
M
to comment
More information about Nikolay Nikolov
More information about Nikolay Nikolov
Nikolay Nikolov
Copy link to comment
20 April 2026 at 14:24
BE 1, QA: 1
Reply
Add thumbs up reaction
Add reaction
Edit...
|
Firefox
|
[JY-20501] Batch initial sync for Hubspot - Jira — [JY-20501] Batch initial sync for Hubspot - Jira — Work...
|
jiminny.atlassian.net/browse/JY-20501
|
74393
|
|
74394
|
Platform Team - Backlog - Jira
Service-Desk - Queu Platform Team - Backlog - Jira
Service-Desk - Queues - Platform team - Service space - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
Close tab
Feed — jiminny — Sentry
Feed — jiminny — Sentry
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
Lukas Kovalik - Time Off
Lukas Kovalik - Time Off
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Sidebar
Sidebar
Top Bar
Top Bar
Main Content
Main Content
Expand sidebar [
Expand sidebar [
Switch sites or apps
Switch sites or apps
Go to your Jira homepage
Search, press enter to navigate to advanced search with your text query
Create
Create
Rovo Ask Rovo
Ask Rovo
Notifications
Notifications
Help
Help
Settings
Settings
[EMAIL]
[EMAIL]
Spaces
Spaces
/
Jiminny (New) Jiminny (New)
Jiminny (New)
/
Epic - Change parent
JY-15971
JY-15971
/
Story - Change work type
JY-20501
JY-20501
Copy link
Batch initial sync for Hubspot- Summary, edit
Batch initial sync for Hubspot
Batch initial sync for Hubspot
Add or create work related to this Story
Add or create work related to this Story
View app actions
View app actions
Collapse Description Description
Collapse Description
Collapse Description
Description
Edit Description, edit
Currently synching initial user profile (opportunities) is not working sufficiently when a huge amount of objects are imported from the CRM into Jiminny.
Problems:
Importing deals can take hours
Solution:
The current
syncOpportunities()
should only read the batches of deals from Hubspot and store the payload in Redis
There should be a separate job
import object
per batches of 100 updated deals which reads the info for objects from Redis and import them in Jiminny
There should be retry mechanism of the jobs so that in case they are using spot instance for processing which is turned off, the job will be retried
We should clean the Redis in 24 hours in case there are objects which are still not processed
Collapse Subtasks Subtasks Work item actions Configure columns Create subtask
Collapse Subtasks
Collapse Subtasks
Subtasks
Work item actions
Work item actions
Configure columns
Configure columns
Create subtask
Create subtask
0
% Done
Work
Work
More actions for Work
More actions for Work
Priority
Priority
More actions for Priority
More actions for Priority
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Edit Priority
Medium
Unassigned- edit Assignee
Unassigned
Ready for Dev - Change status
READY FOR DEV
Work
Work
More actions for Work
More actions for Work
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Priority
Priority
More actions for Priority
More actions for Priority
Edit Priority
Medium
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Unassigned- edit Assignee
Unassigned
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
Ready for Dev - Change status
READY FOR DEV
Collapse Linked work items Linked work items Link a work item
Collapse Linked work items
Collapse Linked work items
Linked work items
Link a work item
Link a work item
clones
clones
JY-20500 is not done
JY-20500
Batch initial sync for Salesforce
Batch initial sync for Salesforce
Backlog - Change status
BACKLOG
Unlink work item
Collapse Activity Activity
Collapse Activity
Collapse Activity
Activity
All
All
Comments
Comments
History
History
Work log
Work log
Atlassian Intelligence Summarise
Summarise
Newest first Newest first
Newest first
Add a comment…
Suggest a reply...
Suggest a reply...
Who is working on this...?
Who is working on this...?
Status update...
Status update...
Pro tip:
press
M
to comment
More information about Nikolay Nikolov
More information about Nikolay Nikolov
Nikolay Nikolov
Copy link to comment
20 April 2026 at 14:24
BE 1, QA: 1
Reply
Add thumbs up reaction
Add reaction
Edit
More actions
More information about Nikolay Nikolov
More information about Nikolay Nikolov
Nikolay Nikolov
Copy link to comment
20 April 2026 at 14:07
Initial Owner/Profile Sync for Opportunities
Initial Owner/Profile Sync for Opportunities
Where It Happens
Where It Happens
Trigger:
ProfileCreated
event →
SyncProfileOpportunities
listener
Turn on wrap
Copy as text
1
User connects to CRM → Profile created → ProfileCreated event
2
↓
3
SyncProfileOpportunities::handle()
4
↓
5
SyncOpportunitiesJob dispatched
Location
Location
SyncProfileOpportunities.php
How It Works
How It Works
Step
Action
1
ProfileCreated
event fires when a new CRM profile is created
2...
|
Firefox
|
[JY-20501] Batch initial sync for Hubspot - Jira — [JY-20501] Batch initial sync for Hubspot - Jira — Work...
|
jiminny.atlassian.net/browse/JY-20501
|
74394
|
|
74395
|
Platform Team - Backlog - Jira
Service-Desk - Queu Platform Team - Backlog - Jira
Service-Desk - Queues - Platform team - Service space - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
Close tab
Feed — jiminny — Sentry
Feed — jiminny — Sentry
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
Lukas Kovalik - Time Off
Lukas Kovalik - Time Off
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Sidebar
Sidebar
Top Bar
Top Bar
Main Content
Main Content
Expand sidebar [
Expand sidebar [
Switch sites or apps
Switch sites or apps
Go to your Jira homepage
Search, press enter to navigate to advanced search with your text query
Create
Create
Rovo Ask Rovo
Ask Rovo
Notifications
Notifications
Help
Help
Settings
Settings
[EMAIL]
[EMAIL]
Spaces
Spaces
/
Jiminny (New) Jiminny (New)
Jiminny (New)
/
Epic - Change parent
JY-15971
JY-15971
/
Story - Change work type
JY-20501
JY-20501
Copy link
Batch initial sync for Hubspot- Summary, edit
Batch initial sync for Hubspot
Batch initial sync for Hubspot
Add or create work related to this Story
Add or create work related to this Story
View app actions
View app actions
Collapse Description Description
Collapse Description
Collapse Description
Description
Edit Description, edit
Currently synching initial user profile (opportunities) is not working sufficiently when a huge amount of objects are imported from the CRM into Jiminny.
Problems:
Importing deals can take hours
Solution:
The current
syncOpportunities()
should only read the batches of deals from Hubspot and store the payload in Redis
There should be a separate job
import object
per batches of 100 updated deals which reads the info for objects from Redis and import them in Jiminny
There should be retry mechanism of the jobs so that in case they are using spot instance for processing which is turned off, the job will be retried
We should clean the Redis in 24 hours in case there are objects which are still not processed
Collapse Subtasks Subtasks Work item actions Configure columns Create subtask
Collapse Subtasks
Collapse Subtasks
Subtasks
Work item actions
Work item actions
Configure columns
Configure columns
Create subtask
Create subtask
0
% Done
Work
Work
More actions for Work
More actions for Work
Priority
Priority
More actions for Priority
More actions for Priority
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Edit Priority
Medium
Unassigned- edit Assignee
Unassigned
Ready for Dev - Change status
READY FOR DEV
Work
Work
More actions for Work
More actions for Work
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Priority
Priority
More actions for Priority
More actions for Priority
Edit Priority
Medium
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Unassigned- edit Assignee
Unassigned
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
Ready for Dev - Change status
READY FOR DEV
Collapse Linked work items Linked work items Link a work item...
|
Firefox
|
[JY-20501] Batch initial sync for Hubspot - Jira — [JY-20501] Batch initial sync for Hubspot - Jira — Work...
|
jiminny.atlassian.net/browse/JY-20501
|
74395
|
|
74396
|
Platform Team - Backlog - Jira
Service-Desk - Queu Platform Team - Backlog - Jira
Service-Desk - Queues - Platform team - Service space - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
Close tab
Feed — jiminny — Sentry
Feed — jiminny — Sentry
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
Lukas Kovalik - Time Off
Lukas Kovalik - Time Off
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Sidebar
Sidebar
Top Bar
Top Bar
Main Content
Main Content
Expand sidebar [
Expand sidebar [
Switch sites or apps
Switch sites or apps
Go to your Jira homepage
Search, press enter to navigate to advanced search with your text query
Create
Create
Rovo Ask Rovo
Ask Rovo
Notifications
Notifications
Help
Help
Settings
Settings
[EMAIL]
[EMAIL]
Spaces
Spaces
/
Jiminny (New) Jiminny (New)
Jiminny (New)
/
Epic - Change parent
JY-15971
JY-15971
/
Story - Change work type
JY-20501
JY-20501
Copy link
Batch initial sync for Hubspot- Summary, edit
Batch initial sync for Hubspot
Batch initial sync for Hubspot
Add or create work related to this Story
Add or create work related to this Story
View app actions
View app actions
Collapse Description Description
Collapse Description
Collapse Description
Description
Edit Description, edit
Currently synching initial user profile (opportunities) is not working sufficiently when a huge amount of objects are imported from the CRM into Jiminny.
Problems:
Importing deals can take hours
Solution:
The current
syncOpportunities()
should only read the batches of deals from Hubspot and store the payload in Redis
There should be a separate job
import object
per batches of 100 updated deals which reads the info for objects from Redis and import them in Jiminny
There should be retry mechanism of the jobs so that in case they are using spot instance for processing which is turned off, the job will be retried
We should clean the Redis in 24 hours in case there are objects which are still not processed
Collapse Subtasks Subtasks Work item actions Configure columns Create subtask
Collapse Subtasks
Collapse Subtasks
Subtasks
Work item actions
Work item actions
Configure columns
Configure columns
Create subtask
Create subtask
0
% Done
Work
Work
More actions for Work
More actions for Work
Priority
Priority
More actions for Priority
More actions for Priority
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Edit Priority
Medium
Unassigned- edit Assignee
Unassigned
Ready for Dev - Change status
READY FOR DEV
Work
Work
More actions for Work
More actions for Work
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Priority
Priority
More actions for Priority
More actions for Priority
Edit Priority
Medium
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Unassigned- edit Assignee
Unassigned
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
Ready for Dev - Change status
READY FOR DEV
Collapse Linked work items Linked work items Link a work item
Collapse Linked work items
Collapse Linked work items
Linked work items
Link a work item
Link a work item
clones
clones
JY-20500 is not done
JY-20500
Batch initial sync for Salesforce
Batch initial sync for Salesforce
Backlog - Change status
BACKLOG
Unlink work item
Collapse Activity Activity
Collapse Activity
Collapse Activity
Activity
All
All
Comments
Comments
History
History
Work log
Work log
Atlassian Intelligence Summarise
Summarise
Newest first Newest first
Newest first
Add a comment…
Suggest a reply...
Suggest a reply...
Who is working on this...?
Who is working on this...?
Status update...
Status update...
Pro tip:
press
M
to comment
More information about Nikolay Nikolov
More information about Nikolay Nikolov
Nikolay Nikolov
Copy link to comment
20 April 2026 at 14:24
BE 1, QA: 1
Reply
Add thumbs up reaction
Add reaction
Edit
More actions
More information about Nikolay Nikolov
More information about Nikolay Nikolov
Nikolay Nikolov
Copy link to comment
20 April 2026 at 14:07
Initial Owner/Profile Sync for Opportunities
Initial Owner/Profile Sync for Opportunities
Where It Happens
Where It Happens
Trigger:
ProfileCreated
event →
SyncProfileOpportunities
listener
Turn on wrap
Copy as text
1
User connects to CRM → Profile created → ProfileCreated event
2
↓
3
SyncProfileOpportunities::handle()
4
↓
5
SyncOpportunitiesJob dispatched
Location
Location
SyncProfileOpportunities.php
How It Works
How It Works
Step
Action
1
ProfileCreated
event fires when a new CRM profile is created
2
SyncProfileOpportunities
listener handles it
3
Dispatches
SyncOpportunitiesJob
with
crm_profile_id
parameter
4
Uses
LAST_MODIFIED_BY_PROFILE_SYNC_OPPORTUNITY_STRATEGY
Step
1
2
3
4
Action
ProfileCreated
event fires when a new CRM profile is created...
|
Firefox
|
[JY-20501] Batch initial sync for Hubspot - Jira — [JY-20501] Batch initial sync for Hubspot - Jira — Work...
|
jiminny.atlassian.net/browse/JY-20501
|
74396
|
|
74397
|
Platform Team - Backlog - Jira
Service-Desk - Queu Platform Team - Backlog - Jira
Service-Desk - Queues - Platform team - Service space - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
Close tab
Feed — jiminny — Sentry
Feed — jiminny — Sentry
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
Lukas Kovalik - Time Off
Lukas Kovalik - Time Off
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Sidebar
Sidebar
Top Bar
Top Bar
Main Content
Main Content
Expand sidebar [
Expand sidebar [
Switch sites or apps
Switch sites or apps
Go to your Jira homepage
Search, press enter to navigate to advanced search with your text query
Create
Create
Rovo Ask Rovo
Ask Rovo
Notifications
Notifications
Help
Help
Settings
Settings
[EMAIL]
[EMAIL]
Spaces
Spaces
/
Jiminny (New) Jiminny (New)
Jiminny (New)
/
Epic - Change parent
JY-15971
JY-15971
/
Story - Change work type
JY-20501
JY-20501
Copy link
Batch initial sync for Hubspot- Summary, edit
Batch initial sync for Hubspot
Batch initial sync for Hubspot
Add or create work related to this Story
Add or create work related to this Story
View app actions
View app actions
Collapse Description Description
Collapse Description
Collapse Description
Description
Edit Description, edit
Currently synching initial user profile (opportunities) is not working sufficiently when a huge amount of objects are imported from the CRM into Jiminny.
Problems:
Importing deals can take hours
Solution:
The current
syncOpportunities()
should only read the batches of deals from Hubspot and store the payload in Redis
There should be a separate job
import object
per batches of 100 updated deals which reads the info for objects from Redis and import them in Jiminny
There should be retry mechanism of the jobs so that in case they are using spot instance for processing which is turned off, the job will be retried
We should clean the Redis in 24 hours in case there are objects which are still not processed
Collapse Subtasks Subtasks Work item actions Configure columns Create subtask
Collapse Subtasks
Collapse Subtasks
Subtasks
Work item actions
Work item actions
Configure columns
Configure columns
Create subtask
Create subtask
0
% Done
Work
Work
More actions for Work
More actions for Work
Priority
Priority
More actions for Priority
More actions for Priority
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Edit Priority
Medium
Unassigned- edit Assignee
Unassigned
Ready for Dev - Change status
READY FOR DEV
Work
Work
More actions for Work
More actions for Work
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Priority
Priority
More actions for Priority
More actions for Priority
Edit Priority
Medium
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Unassigned- edit Assignee
Unassigned
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
Ready for Dev - Change status
READY FOR DEV
Collapse Linked work items Linked work items Link a work item
Collapse Linked work items
Collapse Linked work items
Linked work items
Link a work item
Link a work item
clones
clones
JY-20500 is not done
JY-20500
Batch initial sync for Salesforce
Batch initial sync for Salesforce
Backlog - Change status
BACKLOG
Unlink work item
Collapse Activity Activity
Collapse Activity
Collapse Activity
Activity
All
All
Comments
Comments
History
History
Work log
Work log
Atlassian Intelligence Summarise
Summarise
Newest first Newest first
Newest first
Add a comment…
Suggest a reply...
Suggest a reply...
Who is working on this...?
Who is working on this...?
Status update...
Status update...
Pro tip:
press
M
to comment
More information about Nikolay Nikolov
More information about Nikolay Nikolov
Nikolay Nikolov
Copy link to comment
20 April 2026 at 14:24
BE 1, QA: 1
Reply
Add thumbs up reaction
Add reaction
Edit
More actions
More information about Nikolay Nikolov
More information about Nikolay Nikolov
Nikolay Nikolov
Copy link to comment
20 April 2026 at 14:07
Initial Owner/Profile Sync for Opportunities
Initial Owner/Profile Sync for Opportunities
Where It Happens
Where It Happens
Trigger:
ProfileCreated
event →
SyncProfileOpportunities
listener
Turn on wrap
Copy as text
1
User connects to CRM → Profile created → ProfileCreated event
2
↓
3
SyncProfileOpportunities::handle()
4
↓
5
SyncOpportunitiesJob dispatched
Location
Location
SyncProfileOpportunities.php
How It Works
How It Works
Step
Action
1
ProfileCreated
event fires when a new CRM profile is created...
|
Firefox
|
[JY-20501] Batch initial sync for Hubspot - Jira — [JY-20501] Batch initial sync for Hubspot - Jira — Work...
|
jiminny.atlassian.net/browse/JY-20501
|
74397
|
|
74398
|
Platform Team - Backlog - Jira
Service-Desk - Queu Platform Team - Backlog - Jira
Service-Desk - Queues - Platform team - Service space - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
[JY-20501] Batch initial sync for Hubspot - Jira
Close tab
Feed — jiminny — Sentry
Feed — jiminny — Sentry
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
JY-20963 fix deleted object import by LakyLak · Pull Request #12121 · jiminny/app
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
Lukas Kovalik - Time Off
Lukas Kovalik - Time Off
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Skip to:
Sidebar
Sidebar
Top Bar
Top Bar
Main Content
Main Content
Expand sidebar [
Expand sidebar [
Switch sites or apps
Switch sites or apps
Go to your Jira homepage
Search, press enter to navigate to advanced search with your text query
Create
Create
Rovo Ask Rovo
Ask Rovo
Notifications
Notifications
Help
Help
Settings
Settings
[EMAIL]
[EMAIL]
Spaces
Spaces
/
Jiminny (New) Jiminny (New)
Jiminny (New)
/
Epic - Change parent
JY-15971
JY-15971
/
Story - Change work type
JY-20501
JY-20501
Copy link
Batch initial sync for Hubspot- Summary, edit
Batch initial sync for Hubspot
Batch initial sync for Hubspot
Add or create work related to this Story
Add or create work related to this Story
View app actions
View app actions
Collapse Description Description
Collapse Description
Collapse Description
Description
Edit Description, edit
Currently synching initial user profile (opportunities) is not working sufficiently when a huge amount of objects are imported from the CRM into Jiminny.
Problems:
Importing deals can take hours
Solution:
The current
syncOpportunities()
should only read the batches of deals from Hubspot and store the payload in Redis
There should be a separate job
import object
per batches of 100 updated deals which reads the info for objects from Redis and import them in Jiminny
There should be retry mechanism of the jobs so that in case they are using spot instance for processing which is turned off, the job will be retried
We should clean the Redis in 24 hours in case there are objects which are still not processed
Collapse Subtasks Subtasks Work item actions Configure columns Create subtask
Collapse Subtasks
Collapse Subtasks
Subtasks
Work item actions
Work item actions
Configure columns
Configure columns
Create subtask
Create subtask
0
% Done
Work
Work
More actions for Work
More actions for Work
Priority
Priority
More actions for Priority
More actions for Priority
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Edit Priority
Medium
Unassigned- edit Assignee
Unassigned
Ready for Dev - Change status
READY FOR DEV
Work
Work
More actions for Work
More actions for Work
JY-20707 is not resolved
JY-20707
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Process in batches HubSpot: In-memory buffer of 800, but still processes via processOpportunityBatch()
Edit Summary
Priority
Priority
More actions for Priority
More actions for Priority
Edit Priority
Medium
Story Points
Story Points
More actions for Story Points
More actions for Story Points
Assignee
Assignee
More actions for Assignee
More actions for Assignee
Unassigned- edit Assignee
Unassigned
Status
Status
Status • Sort in ascending order
Status • Sort in ascending order
More actions for Status
More actions for Status
Ready for Dev - Change status
READY FOR DEV
Collapse Linked work items Linked work items Link a work item
Collapse Linked work items
Collapse Linked work items...
|
Firefox
|
[JY-20501] Batch initial sync for Hubspot - Jira — [JY-20501] Batch initial sync for Hubspot - Jira — Work...
|
jiminny.atlassian.net/browse/JY-20501
|
74398
|