each issue does keep track of history of changes and you can also configure notifications for changed description. There might be a way to configure some fine-grained permissions but instead I would recommend asking your QA team to create new issues when anything changes.
In general, an agile approach to software relies less on locking systems down and more on team communication and trust. The Agile Manifesto is a great idea to discuss with your team: https://agilemanifesto.org
You could also run a Team Health Monitor from our playbook to help your team identify opportunities to improve the ways you are working together. https://www.atlassian.com/team-playbook/health-monitor
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events