6 karma · joined February 8, 2013
It's also those "filters and scripts" you've set up to create your own triage queue that we're trying to replace. The average user should not have to write scripts to receive and process their work in an efficient manner. That's what we're trying to solve at Monolist!
The number of tools used daily is growing, which is in one way beneficial for the worker since they get a better and more specialized tool to do their work. However, it increases fragmentation and the chances of missed work.
Email is the most common solution, but that has its own downsides and seems to be used less and less for daily work. We think the solution is an ever-updating and fully synchronized “command center” for everything across every app you may be using.
2. Yes, as you're describing there are various hypothetical ways to link an email with a pull request or vice versa. But how do you propose the average user implement this? At the end of the day, they'd end up building a subset of the underlying functionality that Monolist provides.
3. Yes, it is "possible" for email clients to support additional features, and many of them do. However, we believe email requires a fundamental rethinking to be valuable again in the workplace.
At Monolist (https://monolist.co), we’re building a streamlined task experience that integrates deeply with Jira (and Confluence) Cloud specifically so you don’t have to deal with these painful UIs.