Closed (fixed)
Project:
Burndown
Version:
1.0.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Reporter:
Created:
12 Jul 2026 at 21:46 UTC
Updated:
13 Jul 2026 at 12:34 UTC
Jump to comment: Most recent
When a task is moved from one column/swimlane to another, there are two notification emails sent.
My guess is that it sends one for the removal of the first column id, and then another for the addition of the new column id. It is hard to detect this because neither email shows the column name.
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
swirtThis is interesting. Moving a task from one column to another, definitely does generate two emails, but only one is related to the column change. The other is from an "edit" just like the column change though it shows no diff change... which leads me to believe the change is in one of the values not tracked by the diff.... maybe log, 'backlog_sort' or 'board_sort? I will have to step through it to see.
Comment #3
swirtComment #4
jeremylichtman commentedI wonder if the ignore field list from the other issue will have fixed this.
Comment #5
swirtConfirmed, I commented out the ignore field check and it is the change to the sort order that triggers the second email. Apparently it is handled by two separate api calls so one move shows up as two different edits because they are different edits.
I can't think of a way for one to know about the other and prevent the double send :(
Since the diff was never showing changed to board sort, what do you think about checking to see if there is no reported changes in the diff, we skip sending an edit email? That would solve the problem of both the double send, and an edit notice with no visible changes.
Comment #7
swirtThis is ready for review and concludes my planned work on email related stuff. So a release can follow.
Comment #9
jeremylichtman commentedMerged. Preparing a release.
Comment #10
jeremylichtman commentedComment #12
jeremylichtman commentedFixed on 1.0.64.