Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #1690

Closed
Open
Created Oct 13, 2012 by Administrator@rootOwner

reassigned_issue_email problem

Created by: exaexa

Hey everyone, I've started seeing "reassigned_issue_email" problems in resque failed log. I found that it happens mostly when I assign an issue that was previously unassigned.

the reassigned_issue_email(recipient_id,issue_id,previous_assignee_id) is then called as (for example):

reassigned_issue_email(12,23,nil)

which results in ActiveRecord error about inability to find the previous assignee user object.

I guess there's some simple fix for that and hope I already described it "enough". If not, please tell me, I'll generate and post detailed error messages.

If this is not a bug, please tell me why. (I'm upgraded to latest stable)

Thanks in advance, -exa

Assignee
Assign to
Time tracking