this is my new task for devops

blah blah

asdbkjsdad

sbckcwqbn

Why the export does not contains the task author?

I have noticed some strange behaviour with recurring events, which I've first documented at Wikimedias Phabricator. It's about what every programmer I know hates: Daylight saving times. Short version is: Phabricator locks time windows of recurring events to the time the event creator had in his time zone settings when he created the event, but does neither give an option to select another time zone to lock to nor does even show which time zone this is currently locked to.

I have many other excellent ideas for the Phacility online swag store, these are my favorite:

@cos, which specific types of fields are you seeing issues with?

The projects attachment should let you get projects, here's an example call on this install to retrieve this task:

I'm not interested in pursuing this, mostly it does not solve the core problem of "too may emails". (see Describing Root Problems) If the problem really is "my boss doesn't want to unsubscribe after a comment", then the problem is too narrow for us to have an upstream solution to. Making it an option is very disruptive to everyone else.

Please file a bug report if the button is not in stable.

In T12314#217334, @shandor wrote:

The interaction between subtypes and "required" flag was mentioned briefly in the weaknesses section, but it's a little unclear how this new feature will work with them. With Custom Forms, we are currently unable to use Required custom fields properly because they are still required fields even when hidden in some particular forms. Do Task Subtypes solve this issue naturally, or is it something that still needs to be implemented?

@dainysunil you need to provide full instructions to reproduce this issue in an untainted environment.

I just realized that in the stable release there is only one button Edit Query. The Use Results... is missing. Are there any plans to be pushed in the stable release soon?

@chad -we tried the upgrade once again .. but the issue is still there

In T10412#161218, @urzds wrote:

In T10412#160950, @epriestley wrote:

Change milestoneNumber in phabricator_project.project to reorder milestones.

Thanks! That worked.

The interaction between subtypes and "required" flag was mentioned briefly in the weaknesses section, but it's a little unclear how this new feature will work with them. With Custom Forms, we are currently unable to use Required custom fields properly because they are still required fields even when hidden in some particular forms. Do Task Subtypes solve this issue naturally, or is it something that still needs to be implemented?

no need for it

Cool thanks for the detailed response.

• The "root problem" from our point of view is a security policy with no technical basis. As a general rule, we do not implement changes to help installs solve problems of their own making, and you have this problem only because of your policy.
• disable_functions = phpinfo does not improve the security of Phabricator, but impairs normal behavior.
• To move forward, you should either: change the policy, obtain an exemption to the policy, fork Phabricator, or select other software which adheres to the policy.

My only guess here is something is corrupt, incomplete, or not upgraded properly. I don't see anything on our side that would lead to this state.

If you believe those are the full, complete steps to reproduce the issue then please take the time and launch a clean test environment and follow the steps and let us know if they are complete.

@chad you need to try upgrade phabricator from branch abff6dc8a9b4e081d74beaf8f062223cb5308ec3 to reproduce the issue. Can you consider this as step to reproduce the error.

We don't accept bug reports without reproduction steps.

Please find the image with upgrade branch. While upgrading the phabricator from this branch we found this error. Please check this upgrade to reproduce the error.

Hmmm, will have another go and delete bits and guess what i did wrong was suggesting a solution..

See Contributing Feature Requests for what we require in a feature request.

fast response, any words as to why this wont be fixed?

I'm now using this and it works well! I've noticed one wrinkle that I don't understand, namely, the 'Details' section when viewing a task includes some custom fields and not others? In particular, it includes custom fields that are hidden for the current task subtype. Is there anyway of controlling what appears here?

This hasn't seen activity in four months so I'm sending it to the murky depths.

Oh, yeah, in Conpherence you'd have to like :+3+space+delete+⏎ or something.

Ah true, this was SOE issue I guess.

Can you just type :+3+Space?

To go at my problem from a different angle: I would also happily settle for the ability to do and save a search of commits on a specific branch. (although my goal was to include commits on master from this repo and commits from other repos cause while we have a product monorepo we have other repos for tools, experiments, etc)

bin/search init warns me that the index is "incorrect". It might be more clear to distinguish between "missing" and "incorrect", since it's more comforting to users to see "everything is as we expect, doing normal first-time setup now" than "something is wrong, fixing it".

In fact this is totally undermining the utility of my attempt at a recent commits dashboard... the panel's window is now entirely filled with such commits from the last minute

Thanks for tryout out this workflow!