Have you possibly changed mailers from "SES" to "SES via SMTP" or something like that? The logic here is basically:
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Mar 13 2019
This also probably fixes a couple of minor bugs. For example, I suspect this is currently a bug, although I haven't verified it:
Herald rules may "Require Secure Mail", but we won't know that at the time we're building mail about the indirect change to "Y". This is a problem in practice.
See also https://phabricator.wikimedia.org/T113556 downstream.
See PHI1125. Recent versions of JIRA (JIRA 8?) still work with approximately the same instructions, but you have to fill out a modal dialog with about 7 required fields first, and none of the fields have real values. That is, the configuration instructions for recent JIRA are:
I'm going to consider this resolved at this point. The one thing I haven't built is the "task/point count" from the mocks (on the right-hand side of the header, counting points in each group), but I think this is probably only of much use under "Group by Owner", and maybe not even then. I'm open to building this in a future iteration and it's not likely to be very much work, I'd just like to see feedback that we're generally headed in the right direction first and that the element would have real-world use cases.
Very very disappointed. "Import from LDAP" worked very well and we use that almost every week for importing newly added employees. Though it's ok that employees register themself, but it changed our existing workflow in our company.
Mar 12 2019
- Use "fa-map-pin", which I guess is sort of a pun about "points" on a map?
This is still a little more sensical than changing the date created though, isn't it?
This is a static sorting (like "By Date Created") where you can't change point values by dragging.
- Typo correction.
Oh, I didn't submit this comment:
In D20264#254338, @epriestley wrote:I think I lean toward "yeah, let's get rid of this" after sleeping on it.
Currently, you can put a task in a column in these ways:
Currently, expected behavior.
More or less resolved previously in D14918.
D19549 added Spaces support to projects.
Mooted by D20263, which removes the rarely-used drag functionality from global lists.