The article title does not fully match the content. A more appropriate title would be: "In the issue tracker, write issues, not user stories".
The primary call to action here is to separate product-level details (including "user experience") from the issue tracker. The difference lies between the holistic view required for product-level work and the need for a clearly defined scope for tasks and issues.
The primary call to action here is to separate product-level details (including "user experience") from the issue tracker. The difference lies between the holistic view required for product-level work and the need for a clearly defined scope for tasks and issues.