[carlisle_]

Can you explain why it’s necessary I need to write a ticket to update documentation?

[disgruntledphd2]

I think he did, and the answer is SOC compliance. I learned something about this compliance from his comment, and it'll encourage me to write these tickets next time (my current org is going through this process right now).

[sanderjd]

Which comment? The one in this thread doesn't seem to explain this. Does SOC require a Jira ticket for every change or does it require an audit trail? If the former, that's stupid, I'm happy to comply with stupid regulations, but I'm not going to gaslight myself into thinking they aren't stupid. If it's the latter, then that makes perfect sense as a regulation, but the commit history of the repo or whatever other versioning system you use for your documentation system can meet that requirement.

[treis]

I did. To give your team visibility into what you're doing and why.

[sanderjd]

Why does my team need to know that I spent two minutes fixing typos in engineering documentation? Also, if they do want to know this, they can subscribe to the changes being made to the documentation repository / system and then they'll see what I did.

Is this really for visibility within my team? Or is it for some kind of external visibility?

[carlisle_]

And the PR doesn’t do that?