/etc/horde/whups/conf.xml is in php-horde-whups 3.0.0~beta1-1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 | <?xml version="1.0"?>
<!-- $Id: 56c6fd76ea2179142484c6e1ae4147df8b7ab6bf $ -->
<configuration>
<configtab name="tickets" desc="Tickets Driver Settings">
<configsection name="tickets">
<configswitch name="driver" desc="What storage driver should we use?">Sql
<case name="Sql" desc="SQL">
<configsection name="params">
<configsql switchname="driverconfig"/>
</configsection>
</case>
</configswitch>
</configsection>
</configtab>
<configtab name="guests" desc="Guest Settings">
<configsection name="guests">
<configswitch name="captcha" quote="false" desc="Require guests to enter a
verification string with each transaction to protect against spam? (Requires
Horde 3.1)">false
<case name="false" desc="No"/>
<case name="true" desc="Yes">
<configstring name="figlet_font" desc="The path to a Figlet
(http://www.figlet.org/) font
file">/usr/share/games/figlet/fonts/big.flf</configstring>
</case>
</configswitch>
</configsection>
</configtab>
<configtab name="mail" desc="Email Settings">
<configsection name="mail">
<configstring name="from_addr" required="false" desc="What email address
should be used to send ticket email? If this is left empty, email will come
from the user who updated the ticket, as long as we can find an email
address for them. You can specify individual email addresses in the queue
administration that will override this setting."/>
<configstring name="return_path" required="false" desc="What email address
should be used for the Return-Path: header when sending ticket email? If you
set up Whups to receive emails with the whups-mail-filter script, you should
set this field to a different address than the from_addr setting, so that
message bounces cannot generate a mail loop."/>
<configstring name="always_copy" required="false" desc="Should we always
send ticket email to one or more addresses? Listeners for the ticket will
always get email as configured below; this is for archiving purposes or for
a tracking list, etc. Seperate multiple email addresses with commas. It is
possible to send to queue specific mail addresses by using the placeholder
'<@>' which will be replaced by the queue name."/>
<configboolean name="reply" desc="Can users reply to ticket emails? If you
entered an email address above, and have configured it to accept ticket
email, enable this. Otherwise, or if you're not sure, leave it disabled."
required="false">false</configboolean>
<configboolean name="include_headers" desc="When generating new tickets or
adding ticket comments from email messages, should we include the basic
email headers into the ticket comment?"
required="false">false</configboolean>
<configboolean name="attach_message" desc="When generating new tickets or
adding ticket comments from email messages, should we include the raw
message as an attachment into the ticket comment?"
required="false">false</configboolean>
<configenum name="commenthistory" desc="When someone adds a comment to a
ticket, how should we send the comments?">new
<values>
<value desc="Only the new comment">new</value>
<value desc="All comments, oldest comments first">chronological</value>
<value desc="All comments, most recent comments
first">revchronological</value>
</values>
</configenum>
<configboolean name="link_attach" desc="Should ticket emails contain
download links for uploaded attachments instead of the attachment
itself?">false</configboolean>
<configboolean name="incl_resp" desc="Should all users responsible for a
queue continue to receive email once a ticket is
assigned?" required="false">true</configboolean>
<configstring name="server_name" desc="What server name should be used to
create ticket links if using
scripts/mail-filter.php?">127.0.0.1</configstring>
<configinteger name="server_port" desc="What server port should be used to
create ticket links if using
scripts/mail-filter.php?">80</configinteger>
<configstring name="username" desc="What user should be used to create
tickets if using scripts/mail-filter.php?" required="false" />
</configsection>
</configtab>
<configtab name="prefs" desc="User Preference Attributes and Menu">
<configsection name="prefs">
<configheader>User Preference Attributes</configheader>
<configstring name="autolink_terms" desc="Users can opt to automatically
link to other tickets referenced in comments. The regex option allows you
to specify one or more phrases to match against along with a number
(i.e. Ticket 101). Note the search is NOT case sensitive. Separate more
than one term with '|'.">bug|ticket|issue</configstring>
<configboolean name="assign_all_groups" desc="Allow assignment to any
group? Assignment of bugs to groups can be limited to groups that users are
members of by disabling this option" required="false">false</configboolean>
</configsection>
</configtab>
<configtab name="defaults" desc="Default States">
<configsection name="states">
<configsection name="1">
<configswitch name="active" desc="1st state">active
<configcase name="inactive" desc="Inactive" />
<configcase name="active" desc="Active">
<configstring name="name" desc="1. State
name">Unconfirmed</configstring>
<configstring name="desc" desc="Description for this state">A ticket has been reported but not yet analyzed</configstring>
<configenum name="category" desc="Category for this new
state">unconfirmed
<values>
<value desc="--"/>
<value desc="Unconfirmed">unconfirmed</value>
<value desc="New">new</value>
<value desc="Assigned">assigned</value>
<value desc="Resolved">resolved</value>
</values>
</configenum>
</configcase>
</configswitch>
</configsection>
<configsection name="2">
<configswitch name="active" desc="2nd state">active
<configcase name="inactive" desc="Inactive" />
<configcase name="active" desc="Active">
<configstring name="name" desc="2. State name">Accepted</configstring>
<configstring name="desc" desc="Description for this state">The ticket has been analyzed and accepted as valid.</configstring>
<configenum name="category" desc="Category for this new state">new
<values>
<value desc="--"/>
<value desc="Unconfirmed">unconfirmed</value>
<value desc="New">new</value>
<value desc="Assigned">assigned</value>
<value desc="Resolved">resolved</value>
</values>
</configenum>
</configcase>
</configswitch>
</configsection>
<configsection name="3">
<configswitch name="active" desc="3rd state">active
<configcase name="inactive" desc="Inactive" />
<configcase name="active" desc="Active">
<configstring name="name" desc="3. State name">Assigned</configstring>
<configstring name="desc" desc="Description for this state">Someone has accepted responsibility for the ticket.</configstring>
<configenum name="category" desc="Category for this new state">assigned
<values>
<value desc="--"/>
<value desc="Unconfirmed">unconfirmed</value>
<value desc="New">new</value>
<value desc="Assigned">assigned</value>
<value desc="Resolved">resolved</value>
</values>
</configenum>
</configcase>
</configswitch>
</configsection>
<configsection name="4">
<configswitch name="active" desc="4th state">active
<configcase name="inactive" desc="Inactive" />
<configcase name="active" desc="Active">
<configstring name="name" desc="4. State name">Resolved</configstring>
<configstring name="desc" desc="Description for this state">The ticket has been resolved.</configstring>
<configenum name="category" desc="Category for this new state">resolved
<values>
<value desc="--"/>
<value desc="Unconfirmed">unconfirmed</value>
<value desc="New">new</value>
<value desc="Assigned">assigned</value>
<value desc="Resolved">resolved</value>
</values>
</configenum>
</configcase>
</configswitch>
</configsection>
<configsection name="5">
<configswitch name="active" desc="5th state">active
<configcase name="inactive" desc="Inactive" />
<configcase name="active" desc="Active">
<configstring name="name" desc="5. State name">Canceled</configstring>
<configstring name="desc" desc="Description for this state">The ticket is no longer valid for one reason or another.</configstring>
<configenum name="category" desc="Category for this new state">resolved
<values>
<value desc="--"/>
<value desc="Unconfirmed">unconfirmed</value>
<value desc="New">new</value>
<value desc="Assigned">assigned</value>
<value desc="Resolved">resolved</value>
</values>
</configenum>
</configcase>
</configswitch>
</configsection>
<configsection name="6">
<configswitch name="active" desc="6th state">inactive
<configcase name="inactive" desc="Inactive" />
<configcase name="active" desc="Active">
<configstring name="name" desc="6. state name"/>
<configstring name="desc" desc="Description for this
state"/>
<configenum name="category" desc="Category for this new state">
<values>
<value desc="--"/>
<value desc="Unconfirmed">unconfirmed</value>
<value desc="New">new</value>
<value desc="Assigned">assigned</value>
<value desc="Resolved">resolved</value>
</values>
</configenum>
</configcase>
</configswitch>
</configsection>
<configsection name="7">
<configswitch name="active" desc="7th state">inactive
<configcase name="inactive" desc="Inactive" />
<configcase name="active" desc="Active">
<configstring name="name" desc="7. state name"/>
<configstring name="desc" desc="Description for this
state"/>
<configenum name="category" desc="Category for this new state">
<values>
<value desc="--"/>
<value desc="Unconfirmed">unconfirmed</value>
<value desc="New">new</value>
<value desc="Assigned">assigned</value>
<value desc="Resolved">resolved</value>
</values>
</configenum>
</configcase>
</configswitch>
</configsection>
<configsection name="8">
<configswitch name="active" desc="8th state">inactive
<configcase name="inactive" desc="Inactive" />
<configcase name="active" desc="Active">
<configstring name="name" desc="8. state name"/>
<configstring name="desc" desc="Description for this
state"/>
<configenum name="category" desc="Category for this new state">
<values>
<value desc="--"/>
<value desc="Unconfirmed">unconfirmed</value>
<value desc="New">new</value>
<value desc="Assigned">assigned</value>
<value desc="Resolved">resolved</value>
</values>
</configenum>
</configcase>
</configswitch>
</configsection>
</configsection>
</configtab>
<configtab name="priorities" desc="Default Priorities">
<configsection name="priorities">
<configsection name="1">
<configswitch name="active" desc="1st priority">active
<configcase name="inactive" desc="Inactive" />
<configcase name="active" desc="Active">
<configstring name="name" desc="1. Priority name">1. Low</configstring>
<configstring name="desc" desc="Description for this priority">This is a very low priority ticket</configstring>
</configcase>
</configswitch>
</configsection>
<configsection name="2">
<configswitch name="active" desc="2nd priority">active
<configcase name="inactive" desc="Inactive" />
<configcase name="active" desc="Active">
<configstring name="name" desc="2. Priority
name">2. Medium</configstring>
<configstring name="desc" desc="Description for this priority">This is an important task, but not urgent.</configstring>
</configcase>
</configswitch>
</configsection>
<configsection name="3">
<configswitch name="active" desc="3rd priority">active
<configcase name="inactive" desc="Inactive" />
<configcase name="active" desc="Active">
<configstring name="name" desc="3. Priority name">3. High</configstring>
<configstring name="desc" desc="Description for this priority">This ticket is very urgent</configstring>
</configcase>
</configswitch>
</configsection>
<configsection name="4">
<configswitch name="active" desc="4th priority">inactive
<configcase name="inactive" desc="Inactive" />
<configcase name="active" desc="Active">
<configstring name="name" desc="4. Priority name"/>
<configstring name="desc" desc="Description for this
priority"/>
</configcase>
</configswitch>
</configsection>
<configsection name="5">
<configswitch name="active" desc="5th priority">inactive
<configcase name="inactive" desc="Inactive" />
<configcase name="active" desc="Active">
<configstring name="name" desc="5. Priority name"/>
<configstring name="desc" desc="Description for this
priority"/>
</configcase>
</configswitch>
</configsection>
<configsection name="6">
<configswitch name="active" desc="6th priority">inactive
<configcase name="inactive" desc="Inactive" />
<configcase name="active" desc="Active">
<configstring name="name" desc="6. Priority name"/>
<configstring name="desc" desc="Description for this
priority"/>
</configcase>
</configswitch>
</configsection>
</configsection>
</configtab>
</configuration>
|