Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
This is where the mindset of "Jira is all you need to document" fails. This is not a knock against Jira but a knock on the philosophy that a backlog of Jira issues is all you need. A living functional doc/design doc/whatever works doc outside of Jira (or whatever tool) can be invaluable to provide an amalgamated picture of the end goal of all those issues. Scrum/Jira dogmatists seem to frown on this more often than not, though.
The tickets created by the PM are out of a well constructed offer the customer signed (29 pages of who is expected to do what and milestones etc.). This works really good for us as we always can refer to the offer and only do what is discussed there. Everything else is in addition and creates costs.
We had to extract additional tasks out of the comments in the first place.