|
|
|
|
|
by addorai
1616 days ago
|
|
The workflow that many teams use (myself included) is to iterate on detailed requirements in a doc, often in a table. They do this so that they can iterate on them in a more collaborative place vs Jira/Linear. It's also more accessible to the broader team (sales, design, marketing, etc). Then after aligning they copy + paste those requirements into the issue tracker. They often also include a link back to the doc. But then you have two places that show the same requirements, one for eng and one for others and they almost always get out of sync. Plus it's a bit annoying for eng to have to parse thru the spec to map requirements for a specific ticket. This is the workflow we're solving for! As for Linear + Notion or Jira integration, it's entirely possible they add it but our approach is to focus on a few product team focused integrations and go deep on them |
|