Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Atlassian integration not loading Jira tasks in Poker meetings #10487

Closed
rafaelromcar-parabol opened this issue Nov 15, 2024 · 0 comments · Fixed by #10488 or #10490
Closed

Atlassian integration not loading Jira tasks in Poker meetings #10487

rafaelromcar-parabol opened this issue Nov 15, 2024 · 0 comments · Fixed by #10488 or #10490
Labels
bug p1 Needs to be addressed fast. Such an issue significantly impacts the majority of users

Comments

@rafaelromcar-parabol
Copy link
Contributor

rafaelromcar-parabol commented Nov 15, 2024

Issue - Bug

  • How serious is the bug? P1
  • OS: macOS / Linux / Windows / ?
  • Browser: Chrome / Safari / Lynx / ? + version
  • Node version: node --version
  • NPM version: npm --version

At least two clients (one and two) this morning shared their struggles on their Poker meetings.

https://www.loom.com/share/ce556b31da9641e187353712964f5766

Sentry link

The error on server side is

SEND TO SENTRY TypeError: Cannot read properties of undefined (reading 'load')                                                                                                                                     
    at updateJiraImageUrls (/home/node/parabol/dist/gqlExecutor.js:184193:31)                                                                                                                                      
    at /home/node/parabol/dist/gqlExecutor.js:134288:43                                                                                                                                                            
    at Array.map (<anonymous>)                                                                                                                                                                                     
    at Object.issues (/home/node/parabol/dist/gqlExecutor.js:134284:33)                                                                                                                                            
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)                                                                                                                                  
    at async Object.AtlassianIntegrationissuesResolver (/home/node/parabol/dist/gqlExecutor.js:144083:22) {                                                                                                        
  locations: [ { line: 1, column: 285 } ],                                                                                                                                                                         
  path: [ 'viewer', 'teamMember', 'integrations', 'atlassian', 'issues' ]                                                                                                                                          
}

It looks like the bug was introduced between 8.3.1 and 8.4.2. See changes to confirm

Acceptance Criteria (optional)

Users can:

  • Load Jira issues on the Sprint Poker meetings

    Triage is performed to find the root cause of the bug, timeboxed to ~1 hour.

Estimated effort: 1 hour to triage. More if root cause is already identified.

@rafaelromcar-parabol rafaelromcar-parabol added bug p1 Needs to be addressed fast. Such an issue significantly impacts the majority of users labels Nov 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug p1 Needs to be addressed fast. Such an issue significantly impacts the majority of users
Projects
None yet
1 participant