How can I prevent more than one edit session on any specific issue in a JIRA Project?

[Robert Matthews]

We are using JIRA 4.3.4 standalone. Here is my conundrum:

• Multiple people may open the edit screen for a specific issue at the same time.
• Each user will save their changes at different times.
• There are custom fields (free text) that may have text already inserted.

A problem occurs when

• user#1 opens the Edit screen in issue TKT-1 then makes edits to existing text in field A
• user#2 also opens the Edit screen in issue TKT-1 then makes edits to field B (field A contains the original text, but not user#1 edits)
• user#1 saves his edits to field A and exits the issue (field A is now changed with user#1 new edits)
• user#2 completes editing field B and saves his edits, exiting the issue
• HOWEVER, field A has the old (original) text AND LOSES the change by user#1. When user#2 saves his field B changes field A reverts to the original text forcing user#1 to re-edit the issue (if he notices his changes have been reverted.

How can an issue be 'locked' so only one set of edits may be entered at a time?

Even better, can a notice appear to others when an issue is already being edited. Confluence notifies users if a page is already being edited; can JIRA do the same?

[Thomas Schlegel · Accepted solution]

Hi Robert,

this was discussed here: https://answers.atlassian.com/questions/26726/how-to-prevent-concurrent-update-on-same-jira-ticket

Cheers

Thomas