+1 for PieSync
You can achieve this yourself, to a degree. You have to create a RepairShopr notification rule for each tech. Have each tech go get their Slack webhook URL (found in their Slack account), and paste that URL into the "Webhook URL" field of the Techs corresponding Notification rule.
Then check the checkboxes in the Webhook URL column for the types of notifications that Tech should receive.
The result is when you assign a ticket to a Tech, they are notified in their personal Slack channel. And if you put any Private notes on the ticket, they also get those in their personal Slack channel.
That's how we have it setup.
Planned means we want to do it, not that it’s scheduled for a dev to work on yet.
We just scheduled a few tasks that had 70+ votes, we can’t do this before those.
omg yes please.
worksheets are made useless by being tied to a custom field alone?
I'm not sure I understand why if I'm adding custom fields, I also want a worksheet.
Isn't that a little redundant, in that I'm adding two custom things together?
In most cases, I want a worksheet based on a type of work done.
Which would be Issue type.
So why aren't Worksheets tied to Issue type?
And so, as is mentioned here, I think an Issue Type should trigger a Custom Field and/or a Worksheet. ie. Issue Type should be the driver for what Custom Fields and Worksheets appear on a ticket.
And then if Issue Type is made an Automation Action, see my suggestion, then we could automate quite easily having worksheets and custom fields show where they are needed.
For reference: http://feedback.repairshopr.com/forums/165658-general/suggestions/16059274-make-issue-type-an-automation-action
Adding my Upvotes to this Suggestion.