-
Notifications
You must be signed in to change notification settings - Fork 174
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge remote-tracking branch 'origin/update-email-to-pbi-rule' into u…
…pdate-email-to-pbi-rule
- Loading branch information
Showing
1 changed file
with
8 additions
and
8 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -35,7 +35,7 @@ If someone often sends email tasks rather than creating PBIs, kindly suggest the | |
|
||
<!--endintro--> | ||
|
||
:::info | ||
:::info | ||
|
||
Of course, you should use your judgement to decide if the email needs to become a PBI - for example, feedback that contains confidential information, or does not include an actionable task would not go into the backlog. | ||
|
||
|
@@ -69,18 +69,18 @@ It's important that you follow the right steps so that the PBI contains all the | |
|
||
4. Remove any remaining email addresses from the header. | ||
|
||
5. Fill out the Description | ||
5. Fill out the Description | ||
|
||
6. Fill out the Acceptance Criteria, adding: *"Reply 'Done' to the email and also @mention them in the PBI with 'Done'"* | ||
|
||
7. Reply back to the original email saying: *"That's awesome feedback, I've moved it to a PBI: {{ URL }}\ | ||
For future ones, if you have access, please add your comments there 🙂"* | ||
|
||
::: greybox | ||
**From:** Bob Northwind "[email protected]\ | ||
**From:** Bob Northwind "<[email protected]>\ | ||
**Sent:** Thursday, 24 November 2023\ | ||
**To:** Jane Doe "[email protected]"\ | ||
**Cc:** John Davis "[email protected]"; Eliza Northwind "[email protected]"\ | ||
**To:** Jane Doe "<[email protected]>"\ | ||
**Cc:** John Davis "<[email protected]>"; Eliza Northwind "<[email protected]>"\ | ||
**Subject:** TimePro PBI 50209: ☠️ Displaying past employees\ | ||
::: | ||
::: bad | ||
|
@@ -96,7 +96,7 @@ Based on email chain: | |
**Cc:** @JohnDavis @ElizaNorthwind\ | ||
**Subject:** TimePro PBI 50209: ☠️ Displaying past employees\ | ||
::: | ||
::: good | ||
::: good | ||
Figure: Email header with GitHub users tagged and no email addresses | ||
::: | ||
|
||
|
@@ -147,13 +147,13 @@ If you use a ticketing system like Zendesk, you should follow a similar process | |
| | | | ||
| -------- | --- | | ||
| To: | Bob | | ||
| Cc: | Tim, [email protected] | | ||
| Cc: | Tim, <[email protected]> | | ||
| Subject: | Re: Add me to Azure DevOps | | ||
::: email-content | ||
|
||
(zendesking) | ||
|
||
### Hi Bob, | ||
### Hi Bob | ||
|
||
\> 1. Could you please add me to Azure DevOps? | ||
|
||
|