User Tools
onboarding:ticketer:operations_update_form
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| onboarding:ticketer:operations_update_form [2021/07/06 15:51] – wflaherty | onboarding:ticketer:operations_update_form [2021/07/09 10:14] (current) – wflaherty | ||
|---|---|---|---|
| Line 6: | Line 6: | ||
| - | === Latest Update === | + | ==== Latest Update |
| - | The Latest Update field has been a hot topic and something that can easily push a scrum into overtime. | + | The Latest Update field is subject to change. If you are unsure about anything here, please ask the Operations team. |
| The way the Operations Update will update the latest update field is in two ways. | The way the Operations Update will update the latest update field is in two ways. | ||
| Line 16: | Line 16: | ||
| Lets go over some examples. All you have to go is start the update with two spaces and end it with two spaces. Anything in between is used for the update. **The two spaces will be removed from the final Operations Update**, however, the update itself will still exists in the Operations Update. | Lets go over some examples. All you have to go is start the update with two spaces and end it with two spaces. Anything in between is used for the update. **The two spaces will be removed from the final Operations Update**, however, the update itself will still exists in the Operations Update. | ||
| + | |||
| + | Please note for these examples, I'm using ~~ to indicate two spaces. | ||
| 1. Operations Update | 1. Operations Update | ||
| Line 21: | Line 23: | ||
| Hi Dave, | Hi Dave, | ||
| - | | + | ~~This is my update. This is more of my updates.~~ |
| I ended the last sentence with two spaces. So this section won't be in it | I ended the last sentence with two spaces. So this section won't be in it | ||
| Line 36: | Line 38: | ||
| 2. Operations Update | 2. Operations Update | ||
| < | < | ||
| - | We are working on a fix that will involve a few tickets from the dev team. When we hear from the dev team we will have a better explanation of the cause. Until then we are going to mitigate the problem for now with a workaround. More details to follow. | + | We are working on a fix that will involve a few tickets from the dev team.~~When we hear from the dev team we will have a better explanation of the cause. Until then we are going to mitigate the problem for now with a workaround. More details to follow.~~ |
| </ | </ | ||
| Line 47: | Line 49: | ||
| < | < | ||
| We are ready on our side for the install. | We are ready on our side for the install. | ||
| - | | + | ~~Are we still okay for the install on Tuesday at 04:00 PDT? If it doesn' |
| - | If we don't hear anything back we will postpone just in case. | + | If we don't hear anything back we will postpone just in case.~~ |
| Kind regards | Kind regards | ||
| </ | </ | ||
| Line 69: | Line 71: | ||
| 1. Operations Update | 1. Operations Update | ||
| < | < | ||
| - | Hi Dave, | + | Hi Someone, |
| This is my update. This is more of my updates. | This is my update. This is more of my updates. | ||
| Line 76: | Line 78: | ||
| Kind regards, | Kind regards, | ||
| - | Ops | + | The team |
| </ | </ | ||
| Line 87: | Line 89: | ||
| 2. Operations Update | 2. Operations Update | ||
| < | < | ||
| - | We are working on a fix that will involve a few tickets from the dev team. | + | We are working on a fix that will involve a few tickets from the dev team. |
| When we hear from the dev team we will have a better explanation of the cause. | When we hear from the dev team we will have a better explanation of the cause. | ||
| Until then we are going to mitigate the problem for now with a workaround. | Until then we are going to mitigate the problem for now with a workaround. | ||
| - | More details to follow. | + | More details to follow. |
| </ | </ | ||
| Line 101: | Line 103: | ||
| 3. Operations Update | 3. Operations Update | ||
| < | < | ||
| - | Hi John, | + | Hi Person, |
| We are ready on our side for the install. | We are ready on our side for the install. | ||
| Line 107: | Line 109: | ||
| Are we still okay for the install on Tuesday at 04:00 PDT? If it doesn' | Are we still okay for the install on Tuesday at 04:00 PDT? If it doesn' | ||
| - | If we don't hear anything back we will postpone just in case. | + | If we don't hear anything back we will postpone just in case. |
| Kind regards, | Kind regards, | ||
| - | Will | + | Me |
| </ | </ | ||
| Line 122: | Line 124: | ||
| In the original planning there was a final fallback that was if the person who wrote the Operations Update didn't use correct grammer or there wasn't a way to figure what was a paragraph, then the entire Operations Update would go in under the Latest Update. This was later removed. We still have a fallback but it isn't doing anything. | In the original planning there was a final fallback that was if the person who wrote the Operations Update didn't use correct grammer or there wasn't a way to figure what was a paragraph, then the entire Operations Update would go in under the Latest Update. This was later removed. We still have a fallback but it isn't doing anything. | ||
| - | === Sending the emails === | + | ==== Sending the emails |
| When the emails are send there is a slight delay added so that there isn't a database transaction problem with the groovlets running at the same time and blocking one another from saving to the database. This is a side effect of parallelising the scripts, and this is the best way around it. | When the emails are send there is a slight delay added so that there isn't a database transaction problem with the groovlets running at the same time and blocking one another from saving to the database. This is a side effect of parallelising the scripts, and this is the best way around it. | ||
onboarding/ticketer/operations_update_form.1625583061.txt.gz · Last modified: 2021/07/06 15:51 by wflaherty
Page Tools
