Watch for danger.
Apr 25 2018
See PHI612 and elsewhere; using "Take action [the first time this rule matches]" isn't always obvious but is usually a better fit than "When [ thing is created ]" and interacts much better with drafts.
Mar 29 2018
Feb 27 2018
Okay. For the sake of 100% clarity it would be nice if the timeline story did show why the action was taken as it isn't immediately clear (unless you've read the documentation of course) why it was removed.
Feb 26 2018
I'll make a note on T12455, but we might be able to render this timeline story more clearly, e.g. "X added project Y (which automatically removed Z, a subproject)" but I think this is likely fairly natural/obvious in most cases and I'm not sure if it's trivial to completely explain in the timeline.
Ah, that would certainly explain it. Sorry for the noise - when entering this I did wonder if I had missed something as it didn't make sense that a name collision would be able to cause this.
"Plasma on Wayland" is a subproject of "Plasma".
Feb 12 2018
@epriestley Would you guys be open for a patch for this? How would you like to see this implemented in order to be acceptable for you guys?
Feb 10 2018
Feb 9 2018
Feb 8 2018
Feb 6 2018
Feb 5 2018
Jan 29 2018
Jan 26 2018
This is quite old and I have no idea how to reproduce it and thus no idea how to fix it. Locally, I tried a few things and wasn't able to identify a case where the Herald field value differed from my actual project list.