This morning, Caleb Rackliffe mentioned to me that CASSANDRA-15907 involved some code work that has Documentation implications, just to let me know.
I'd like to propose a change to the Cassandra Jira system, to include a field called "Doc Impact" that a developer could check if there is accompanying documentation that should be written. It would help with discovery, so that a corresponding _Documentation%Website_ Jira ticket could be written for the work. At DataStax, I've gone even a step further and added an automation rule that makes a copy of the original ticket if the Doc Impact field is checked. I would love to have that as well, but would be happy just for the Doc Impact field. If Doc Impact was mandatory when a ticket moves from review to merge, for instance, that would be useful, too. Thanks, Lorina Poland
