We need collaborative, real-time editing in the Jira description just like Google Docs or Confluence.
Our team collaboratively creates story acceptance criteria. The meeting includes stakeholders and development team members. Oftentimes, during the meeting, the business stakeholder will be typing and a development team member will include a more technical point. These are lost because they can't be captured right away. The Developer needs to remember to go back into the ticket after the discussion and add his point. (They often don't remember.)
Thank you for reaching out.
Indeed, Jira does not provide a way to handle the issue updates of two or more persons at the same time and implement both, causing one of the updates to be overwritten in the issue.
We have two feature requests to improve this behavior here:
Feel free to vote and watch the suggestion to increase its priority and also receive notifications about any updates.
As a workaround while we work on the implementation of those feature requests, there is an App that can help you identify the persons that are currently viewing the issue and avoid this kind of problem:
Let us know if you have any questions.
Thank you for the response, Petter. The ideas you reference will not solve my issue. Those issues want notification on overwrites and/or prevent multiple edits at the same time. I want the opposite - multiple editing at the same time. So, I think this idea should stand on its own.
I do see where there is value in the ideas referenced. The ideal solution would allow for real-time multiple editing option at the issue level as a toggle. So, the system would generally prevent multiple edits (or lock the issue while there is someone editing) but the user could click a toggle that allows for multiple, synchronous edits.
Thank you for the detailed explanation of the feature you are looking for.
Indeed, the ability to simultaneously edit issues as we have in Confluence would be the ideal scenario, however, Jira is an application way more complex and we would need to change the way we currently index the changes, which might definitely affect its performance.
That being said, we see the point of your requirement and how useful it would be, so I created the following feature request with your Development team, where they can review it and bring more clarity if that feature could be implemented considering our current architecture:
Again, thank you so much for providing such valuable feedback and please make sure to provide these same thoughts in the feature request too, voting and watching it. Additionally, I mentioned this thread in an internal comment to reference this with the feature request and provide our developers more context about your requirement.
Let us know if you have any further questions.