You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When imported users from gitlab doesn't have emails because their accounts are private, the system fully crashes and backstage stops working
TypeError: Cannot read properties of undefined (reading 'email') at /app/node_modules/@janus-idp/backstage-plugin-feedback-backend/dist/cjs/plugin-DV3-jMW_.cjs.js:375:160 at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
Expected Behavior
If there is no email, just don't send email. Or possibility to not send emails and to not use jira, so possibility to just create feedbacks in database
jonatanask
changed the title
Users without email breaking all of the backend part and backstage fully crashes
CRITICAL CRASH - Users without email breaking all of the backend part and backstage fully crashes
May 23, 2024
jonatanask
changed the title
CRITICAL CRASH - Users without email breaking all of the backend part and backstage fully crashes
Feedback plugin - Users without email breaking all of the backend part and backstage fully crashes
May 23, 2024
Describe the bug
https://github.com/janus-idp/backstage-plugins/tree/main/plugins/feedback#readme
https://github.com/janus-idp/backstage-plugins/tree/main/plugins/feedback-backend
When imported users from gitlab doesn't have emails because their accounts are private, the system fully crashes and backstage stops working
TypeError: Cannot read properties of undefined (reading 'email') at /app/node_modules/@janus-idp/backstage-plugin-feedback-backend/dist/cjs/plugin-DV3-jMW_.cjs.js:375:160 at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
Expected Behavior
If there is no email, just don't send email. Or possibility to not send emails and to not use jira, so possibility to just create feedbacks in database
What are the steps to reproduce this bug?
The text was updated successfully, but these errors were encountered: