Page MenuHomec4science
Files F103721464

PhabricatorManiphestConfigOptions.php
No OneTemporary
Actions

File Metadata

Created
Tue, Mar 4, 07:16

PhabricatorManiphestConfigOptions.php
View Options

<?php
final class PhabricatorManiphestConfigOptions
extends PhabricatorApplicationConfigOptions {
public function getName() {
return pht("Maniphest");
}
public function getDescription() {
return pht("Configure Maniphest.");
}
public function getOptions() {
$priority_defaults = array(
100 => array(
'name' => pht('Unbreak Now!'),
'short' => pht('Unbreak!'),
'color' => 'indigo',
),
90 => array(
'name' => pht('Needs Triage'),
'short' => pht('Triage'),
'color' => 'violet',
),
80 => array(
'name' => pht('High'),
'short' => pht('High'),
'color' => 'red',
),
50 => array(
'name' => pht('Normal'),
'short' => pht('Normal'),
'color' => 'orange',
),
25 => array(
'name' => pht('Low'),
'short' => pht('Low'),
'color' => 'yellow',
),
0 => array(
'name' => pht('Wishlist'),
'short' => pht('Wish'),
'color' => 'sky',
),
);
// This is intentionally blank for now, until we can move more Maniphest
// logic to custom fields.
$default_fields = array();
foreach ($default_fields as $key => $enabled) {
$default_fields[$key] = array(
'disabled' => !$enabled,
);
}
$custom_field_type = 'custom:PhabricatorCustomFieldConfigOptionType';
return array(
$this->newOption('maniphest.custom-fields', 'wild', array())
->setSummary(pht("Custom Maniphest fields."))
->setDescription(
pht(
"Array of custom fields for Maniphest tasks. For details on ".
"adding custom fields to Maniphest, see 'Maniphest User Guide: ".
"Adding Custom Fields'."))
->addExample(
'{"mycompany:estimated-hours": {"label": "Estimated Hours", '.
'"type": "int", "caption": "Estimated number of hours this will '.
'take.", "required": false}}',
pht('Valid Setting')),
$this->newOption('maniphest.fields', $custom_field_type, $default_fields)
->setCustomData(id(new ManiphestTask())->getCustomFieldBaseClass())
->setDescription(pht("Select and reorder task fields.")),
$this->newOption('maniphest.priorities', 'wild', $priority_defaults)
->setSummary(pht("Configure Maniphest priority names."))
->setDescription(
pht(
'Allows you to edit or override the default priorities available '.
'in Maniphest, like "High", "Normal" and "Low". The configuration '.
'should contain a map of priority constants to priority '.
'specifications (see defaults below for examples).'.
"\n\n".
'The keys you can define for a priority are:'.
"\n\n".
' - `name` Name of the priority.'."\n".
' - `short` Alternate shorter name, used in UIs where there is '.
' not much space available.'."\n".
' - `color` A color for this priority, like "red" or "blue".'.
"\n\n".
'You can choose which priority is the default for newly created '.
'tasks with `maniphest.default-priority`.')),
$this->newOption('maniphest.default-priority', 'int', 90)
->setSummary(pht("Default task priority for create flows."))
->setDescription(
pht(
"What should the default task priority be in create flows? See ".
"the constants in @{class:ManiphestTaskPriority} for valid ".
"values. Defaults to 'needs triage'.")),
$this->newOption(
'metamta.maniphest.reply-handler-domain',
'string',
null)
->setSummary(pht('Enable replying to tasks via email.'))
->setDescription(
pht(
'You can configure a reply handler domain so that email sent from '.
'Maniphest will have a special "Reply To" address like '.
'"T123+82+af19f@example.com" that allows recipients to reply by '.
'email and interact with tasks. For instructions on configurating '.
'reply handlers, see the article "Configuring Inbound Email" in '.
'the Phabricator documentation. By default, this is set to `null` '.
'and Phabricator will use a generic `noreply@` address or the '.
'address of the acting user instead of a special reply handler '.
'address (see `metamta.default-address`). If you set a domain '.
'here, Phabricator will begin generating private reply handler '.
'addresses. See also `metamta.maniphest.reply-handler` to further '.
'configure behavior. This key should be set to the domain part '.
'after the @, like "example.com".')),
$this->newOption(
'metamta.maniphest.reply-handler',
'class',
'ManiphestReplyHandler')
->setBaseClass('PhabricatorMailReplyHandler')
->setDescription(pht('Override reply handler class.')),
$this->newOption(
'metamta.maniphest.subject-prefix',
'string',
'[Maniphest]')
->setDescription(pht('Subject prefix for Maniphest mail.')),
$this->newOption(
'metamta.maniphest.public-create-email',
'string',
null)
->setSummary(pht('Allow filing bugs via email.'))
->setDescription(
pht(
'You can configure an email address like '.
'"bugs@phabricator.example.com" which will automatically create '.
'Maniphest tasks when users send email to it. This relies on the '.
'"From" address to authenticate users, so it is is not completely '.
'secure. To set this up, enter a complete email address like '.
'"bugs@phabricator.example.com" and then configure mail to that '.
'address so it routed to Phabricator (if you\'ve already '.
'configured reply handlers, you\'re probably already done). See '.
'"Configuring Inbound Email" in the documentation for more '.
'information.')),
$this->newOption(
'metamta.maniphest.default-public-author',
'string',
null)
->setSummary(pht('Username anonymous bugs are filed under.'))
->setDescription(
pht(
'If you enable `metamta.maniphest.public-create-email` and create '.
'an email address like "bugs@phabricator.example.com", it will '.
'default to rejecting mail which doesn\'t come from a known user. '.
'However, you might want to let anyone send email to this '.
'address; to do so, set a default author here (a Phabricator '.
'username). A typical use of this might be to create a "System '.
'Agent" user called "bugs" and use that name here. If you specify '.
'a valid username, mail will always be accepted and used to '.
'create a task, even if the sender is not a system user. The '.
'original email address will be stored in an `From Email` field '.
'on the task.')),
);
}
}

Event Timeline

c4science · Help