We support substitution tags in email templates. In other words, you can replace -name- with the name of your customer - it works a lot like {{name}} in a handlebars template.
I hear a lot of teams have lots of different ways to manage simple repetitive tasks across the team, like Google docs, email lists, schedules and so on. So I built Firesub to try to simplify the work for teams.
For the last year or so I’ve been building a checklist management app for teams called Firesub.
The idea is to help make recurring tasks easy to remember and perform in a consistent way across the team.
It is an app that let you create and manage checklists that you and your team can follow whenever you need to perform a repetitive task like product development, code deployments, code reviews etc.
There is a ton of awesome features like assign people to checklists, scheduled checklists, email notifications when checklists is completed and so on, too much to write here, so please “check it” out. =)
I'v just released a first private beta for a tool to manage reusable checklists like code-review checklists. For you HN readers, if you are interested you can try it out at https://app.firesub.com
Trying it out now. So far, I am enjoying how clean the interface is.
It really feels like a glorified TODO list (or TODO list manager), but I do think that there is potential here. I would recommend adding features that separate it from the usual TODO list, e.g.:
- Add features of flowcharts
-- conditionals (if this then go there)
-- subtasks
- Allow for finer control over the contents of the headers and items
-- Currently, it looks like you can add descriptions which display directly beneath the item or header (and is very clean looking!), but it would be nice if I were able to add html content (consider allowing markdown?)
- I may be using it incorrectly, but I started creating a list and accidentally started the list but kept adding items anyway. Consider adding the ability to add the new tasks from an already-started list to the parent list from which it was created.
- Other things? What are your currently-planned unimplemented features for this application?
I could see myself (and my team) using this application if the bullets above were addressed.
-- Flowcharts
I think I need a bit more data on how users use the app and in what direction I should take the app and features before implementing this, but it's very possible I will in the future.
-- Conditionals
Yes, I'm thinking of adding something like this, but on a higher priority I will add Triggers, so a checklist can be started automatically based on for example, a time interval or a callback over HTTP.
I will also add Outcomes, so you can set up a action that should happen when a checklist is completed, like trigger another checklist.
-- Finder control over headers and items
I will work on this, with the goal of making as simple as possible to get started with the first checklist, but over time be able to use more advanced features for creating items.
-- Extended item details
Markdown is in the backlog. Alos item audit trail, like, Frej changed the description from ... to ... (5 min ago), and so on, so you have a complete track record of changes.
-- Merge items from "started-checklists" to parent checklist.
This is something I'm going to implement pretty soon, so that, when a person perform a checklist and discovers a the need of a new item, or an obsolete existing item, they should not need to make the change first on the active checklist and the same changes on the parent checklist.
-- On the roadmap for the near future
Triggers (se abow), Outcomes, Audit trails for checklists & items, "News feed" and Notifications center is things I have on the roadmap.
When it comes to your valid concern about the safety of pilots using a always-online application I agree with you, that would not be very smart, but nowadays there is technical soulutions around this problem [0]. Alsow it is a hint to everyone who have read the book "The checklist manifesto" by Atul Gawande, I recomend it!
