Plan requirement
| App | Macro Date |
| Subscription | Any Zendesk Support plan |
| Access | Admin |
How a date tag is built, and the ones that cover almost everything a team asks for. Change the numbers to suit.
How a tag is built
Three parts, in order:
- Prefix. Which field to write to. Needed only when you run more than one copy of the app for more than one field.
- Plus or minus. Forwards or backwards in time.
- Selector. The actual instruction: how far, in what unit, and optionally which day.
The examples below assume the built-in due date field and the prefix due_at. The numbers are yours to change.
The tags
| due_at_plus_1d | Tomorrow. |
| due_at_plus_1wd | The next working day. |
| due_at_plus_2w | Two weeks from now. |
| due_at_plus_3m | Three months from now. |
| due_at_plus_5y | Five years from now. |
| due_at_plus_1w_2 | The second day of next week. |
| due_at_plus_1m_5 | The fifth day of next month. |
| due_at_plus_1q_7 | The seventh day of next quarter. |
| due_at_plus_1y_10 | The tenth day of next year. |
The tag removes itself
Once the date is set, the app takes the tag off again. So a ticket that still carries a date tag is one where nothing happened, and that is the first thing to look at when a date does not appear.
Days against working days
A plain day count runs through weekends. wd counts working days and, where a schedule is set, skips holidays too. For anything a customer is waiting on, working days are usually what you mean.
Comments
0 comments
Article is closed for comments.