... | ... | @@ -13,4 +13,12 @@ There's a loose convention with prefixing: |
|
|
* `epic:*` indicates that the issue is part of a multifaceted/goal-oriented initiative
|
|
|
* `needs:*` indicates what work is currently blocking (e.g. `concept approval`, `steps to replicate`, detailed `planning`, implementation, `testing`/review)
|
|
|
|
|
|
There are no labels for fine-grained "priorities" because that's too subjective (i.e. all contributors have different priorities), and it's more objective to say *why* an issue matters (`sig:bug`, `sig:performance`, `regression`). However, there *are* prioritization labels for `priority:critical` and `regression` to signal that an issue merits special consideration in the maintenance/release processes. |
|
|
\ No newline at end of file |
|
|
There are no labels for fine-grained "priorities" because that's too subjective (i.e. all contributors have different priorities), and it's more objective to say *why* an issue matters (`sig:bug`, `sig:performance`, `regression`). However, there *are* prioritization labels for `priority:critical` and `regression` to signal that an issue merits special consideration in the maintenance/release processes.
|
|
|
|
|
|
## Examples
|
|
|
|
|
|
| Description | "What" | "Why" | "How" |
|
|
|
| -- | -- | -- | -- |
|
|
|
| I need to use `superdupermail.com` to send mail-blasts, so I want add a new SMTP AUTH mechanism. | `comp:CiviMail` | `sig:compatibility` | `type:proposal` |
|
|
|
| In "Scheduled Reminders", I get confused because the email-address is split into two fields. Let's use one field (like all other "From" widgets). | `comp:Scheduled Reminder` | `sig:usability` | `type:request` |
|
|
|
| When I add 4 line-items, the total price is incorrect -- by €0.03. Could someone figure out why? | `comp:CiviContribute` | `sig:bug` | `type:request` | |