Skip to content

Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
GitLab
GitLab
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
    • Cycle Analytics
    • Insights
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
    • Locked Files
  • Issues 23,663
    • Issues 23,663
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 844
    • Merge Requests 844
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Security & Compliance
    • Security & Compliance
    • Dependency List
  • Packages
    • Packages
    • Container Registry
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • GitLab.org
  • GitLabGitLab
  • Issues
  • #3783

Closed
Open
Opened Oct 17, 2017 by Alexis@AlexisF
  • Report abuse
  • New issue
Report abuse New issue

Duplicate issues created when users reply to email

Summary

When users receive an email with a comment in an issue if they answer this email, it creates a new issue. Also, if you put in CC or other receivers in email to the Service Desk email, it must add these people to issue participants.

Steps to reproduce

  1. Create or comment an issue.
  2. As user, answer this email and add to this email new receivers or CC.

What is the current bug behavior?

Service Desk creates a new issue with "Re:" or "Fwd:".

What is the expected correct behavior?

It must detect this prefix to avoid creating a lot of duplicated issues.
It must add email receivers or CC to issue participants.

Relevant logs and/or screenshots

Captura_de_pantalla_2017-10-17_11-56-26

GitLab Enterprise Edition 10.1.0-rc1-ee

Edited Oct 10, 2019 by Mark Wood

Related issues

  • Discussion
  • Designs
Assignee
Assign to
12.5
Milestone
12.5
Assign milestone
Time tracking
None
Due date
None
10
Labels
Accepting merge requests Category:Service Desk Enterprise Edition P3 S3 backend bug devops::plan group::certify workflow::In dev
Assign labels
  • View project labels
Reference: gitlab-org/gitlab#3783