I'm going to shill for my current employer, you should checkout Kitemaker[0]. The unique shtick is that our 'issues' are large collaborative documents (we call

I'm going to shill for my current employer, you should checkout Kitemaker[0]. The unique shtick is that our 'issues' are large collaborative documents (we call them work items) and are meant to track deliverables rather than development tasks. The idea is that a work item is created as soon as someone has an idea and all the exploratory work happens in the work item. So it could start with someone writing down how a feature should work, then some designers creating some mock ups based on the discussion. Finally programmers can look at the description and the Figma designs and start implementing, with all the context still available. And since the document is created from the start, the entire team can start commenting throughout the whole process rather than at the very end when the jira ticket is created. It helps avoid stuff like this[1]. I obviously like it, but I am biased :). [0] https://kitemaker.co https://kitemaker.co [1] https://cutlefish.substack.com/p/tbm-1052-what-didnt-end-up-in-jira https://cutlefish.substack.com/p/tbm-1052-what-didnt-end-up-...