See also T9853, which includes an extension to do this.

You can use bin/policy unlock to regain edit permissions of objects. See D7189.

The other aspect of Calendar is that you can't put Calendar events on a project's workboard, which is another area of visibility that we need to see these kind of meetings in.

It is our mistake , it is the problem of my company internet. I try again,every thing is OK. Thank you every much !

This is an amorphous, unfocused task and substantially resolved by profile menus and changes in HEAD or planned in connection with T10054, see also M1450.

See T10180 for additional guidance.

"Subscribe" has been removed entirely, primarily to clarify this distinction. The intent and effect of "Watch" is also now more clear. There is additional guidance available in T10180.

This is now resolved, and you no longer need to be a member of a project to watch it. T10180 has additional guidance about this and related changes.

This does not describe a root problem. See Contributing Feature Requests and Describing Root Problems.

wow. such silence.

Thanks. I figured out that the string in php is utf-8 and the one in json must be unicode. I must convert manually myself. It is now working correctly.

This has been quiet for a while, seems like nothing broke too heavily.

It is actively being developed right now, as per the transaction log. Maniphest, Paste and Owners have already been converted over to the new APIs.

That task has been open since august 2014... I'm not terribly concerned about it getting landed and ruining my day any time soon. And I can hold my own in a rebase, don't worry.

Judging from that merge, you should expect to have rebase conflicts when upgrading in future, since those Conduit updates will replace the existing methods (which your patch is applied on). When that happens, you should probably also be aware that the request parameters to Conduit and the returned response may be different from what you've currently implemented, so you'll need to update your build server system to handle it.

I already fixed it locally already, since it's functionality we needed.

I wouldn't spend time writing a patch for this until @epriestley has weighed in and determined that it's an acceptable feature request and that it would be worth the time to review an external contribution for this (it's possible he'll just write the functionality himself). See Contributing Code.

Sure thing. We have a microservices architecture, and frequently make co-dependent revisions in multiple repositories. Our build system pulls diff information from conduit, and patches all required services before running integration tests. Currently, we can only correctly test the revision which depends on all the other ones, since that information is available. Returning dependencies as well as dependent diffs will allow tests to be run on each diff without failing.

This feature request doesn't describe a problem, see Describing Root Problems. What problem are you trying to solve by accessing this data?

So the preview didn't show the text on multiple lines. :/

It is good to know about the repository reparse command. I could see that being useful.

As I recall, yes. But the only install I'm aware of that uses it (Asana itself) also disables the mail prefix, and might disable subject variance, although I'm not sure.

in Asana, does the title updates the ticket's title?

It makes more sense to use the mail message title in Asana, as the integration is essentially replacing mail. It makes less sense to use it in JIRA, and the object's handle's full name is probably the right string to use. I think it's probably OK to just use that universally.