@csilvers, I think you ran into this too although I wasn't around at the time. Likely fixed in HEAD of master.

I'm going to merge this into T6072, which discusses some of these issues in greater detail.

There is now a Edit Related Tasks → Close as Duplicate action next to the existing Edit Related Tasks → Merge Duplicates In action in the related tasks submenu. This change is live on this install:

Happens on test account too

I tried a couple of other devices in the simulator but couldn't get a repro -- can you try this to get a JS trace?

Let me try my spam account.

Nothing unusual. Latest iPhone/iOS

I can't immediately reproduce this in iOS Simulator or on my physical iPhone 4s. What hardware/OS version are you seeing it on?

Please see Contributing Feature Requests and Describing Root Problems to better understand what we consider to be valid feature requests. Specifically we need to know the root problem that occurred that prompted this request to begin with. Right now all we have for information is that too much email was sent out during some operation. There might be other solutions depending what exactly happened and why, to solve this core problem.

The concern here, though well intended, is that it circumvents the audit-ability we build into Phabticator on purpose. We don't know why users have requested to receive notifications,

I've located the mainframe and uploaded the downloads

@chad: indeed, word-break: break-all on the .differential-diff td element seems to do the trick.

proooobably can just sneak word-break: break-all; in there, but needs some testing.

PhabricatorPasteViewController is the best example for the EditEngine comment thing. Basically, make the comment form generate like Paste does (Maniphest too, although it's more complex). Then you can remove PhamePostCommentController completely.

I promise I did read Contributing Requests before I posted this. 😀

This is unrelated to prose diffs.

T8610 T6874 T1460 are all sort of related here. We want to do a lot more with "Done" comments before exploring things like threading. I'm fairly hesitant that if we do "Done" right, it would be needed.

You've clearly used Phabricator a lot more than I have, but isn't it harder to follow those conversations when 3 of them are interleaved on a single timeline?

If you could look at Contributing Feature Requests and Describing Root Problems and help us better understand the problem that prompted this request, it would be really helpful. In general we prefer to not take feature requests that just say "build X, it's better". We need to keep focused (we're 2 people) on making sure we're solving commonly seen problems.

There is no perfect way to present this information, but chronological is universally understood and usually the most accurate. Having a threaded conversation splinters off topics, making it harder to follow the big picture. New comments can appear anywhere in the timeline.

There are (at least) two axes, time and topic. Line comments can be viewed on either. Generic comments can only be viewed by time, which makes them harder to read.

Regression possibly caused by this: https://phabricator.wikimedia.org/T137394

Why is a chronological order of events "wierd"?

It still seems weird that line comments are threaded but ticket comments aren't.

I'd like to be able to respond specifically to that person/that question the same way I could if they left a line comment.

Just got this 3 times in a row again.

The edit link on the post list is a little weird to me, since Maniphest is the only other application which has it (I think?) and the behavior is different there. In particular, you don't lose your place in the results in Maniphest, but you do in Phame. (I think this was originally added to Maniphest as a stopgap for T1960? But it doesn't address that use case in Phame, and that use case likely does not exist.)

(Leaving this open to remind myself to keep an eye on it.)

D16194 may resolve this. I'll keep an eye on things after the deployment and close this if we don't see any more issues for a bit.

Support Resources has information on how to have general questions answered about Phabricator. Contributing Bug Reports details what information is required for a bug report.

FWIW, the answer to both of your questions before you edited it was yes :p

ignore me - wrong install

Thanks for such a quick response!

Docs regenerate on a cron so this won't actually show up live until sometime tonight, but D16186 has a screenshot.

Thanks for the report, and for including good reproduction steps.

Thanks for fixing it so quickly!

Thanks for the report, and for including detailed reproduction steps. This should be fixed in HEAD of master, and will promote to stable at the end of the week. Let us know if you run into anything else.