Is there a way to see if someone has a JIRA ticket in edit mode?

Question

I have three distinct reasons for such a feature.

* Show how many people are simultaneously editing a given JIRA item.
* Hover over the editing count to find out what user.

1) We have an OpsHub synchronization tool that keeps JIRA and Jama epics and user stories synchronized.  If another JIRA user clicks in the Description text box, the JIRA epic/user story is considered in edit-mode and synchronization will be blocked.  In most programs, one has to click an edit button to be in edit-mode.  In JIRA many people just click on a spot in a sentence to discuss wording with a coworker and don't even know they are in edit-mode.  This is not UX friendly.

2) If multiple people happen to be editing the same JIRA item (there is no lock), they have no idea someone else is editing the same item.  As it turns out, the last user to save trashes the work of the first users that saved.  LOST WORK!

3) If users can see who is simultaneously working on the same JIRA item, they have an opportunity to message them to coordinate contributions without losing work.

All of these issues I cited seem rather "UX Design 101" items.  Most other software products alert users of potential hazards so that they do not lose work.

Will Atlassian consider these UX factors and fix these things?

Nic Brough -Adaptavist- · Answer

Why are your people taking so long to refine issues?

You're completely unclear on whether you are using Cloud or Server here, so I can't generate screenshots, because I don't know which one you are using.  You say cloud and then give us a server version (cloud doesn't have versions, it's always "latest")

But you don't need a screenshot, it really is as simple as "view and issue, look to the bottom right".

You do need to check that the app (it's an Atlassian add on) is enabled though.  Visit https://marketplace.atlassian.com/apps/1211596?tab=overview&hosting=cloud to get it re-installed if it's been removed.

One Media · Answer

Thanks for your responses.

We use JIRA for bugs, but our primary usage is agile epics and user stories.

Most of the "multiple instances open for edit" are for user stories as they get refined.  Also people tend to unknowing go into edit mode by clicking in the Description rich text box.

Most don't think to close an edit because they don't realize they are in edit-mode to start with.

@Nic Brough -Adaptavist- Please show a graphic of the item you are referring to below.  I don't see anything like this (unless administratively disabled).  Using cloud version

Jira v8.13.22

"There is a "who is looking" function now, which can tell you whether someone else might be editing an issue. Look to the bottom right of the issue view."

Nic Brough -Adaptavist- · Answer

Welcome to the Atlassian Community!

As an issue tracker, Jira is not expected to have significant concurrency issues, unless basically, you're using it for purposes other than issue tracking.  I've seen concurrency issues dozens of times, but that's almost 20 years of looking after Jira sysatems, and with hundreds of millions of issues, with a number of users I don't care to guess at.  , and all of them were down to either poor process, or people not knowing that it's not built to handle it (start changes, get distracted, come back later after someone else had made an update).

There is an easy "fix", but I am not going to repeat what @Sachin Dhamale said already.

On your specific points

* In the past, you had to click Edit to update any issue, and you still can.  Atlassian added inline field edits directly a few years ago, because having to go into edit mode to change something is clunky and slow (direct inline edit is ideal for an issue tracker).  The UX for that is as friendly as you can make it - it enables people to update things without having to think.
* When there is a clash, nothing is lost.  * Both edits are recorded in the history.  
* If you put a lock in place, you'd have the problem that your issues gradually all become unusable.  A lock is completely the wrong solution to this problem.

* There is a "who is looking" function now, which can tell you whether someone else might be editing an issue.  Look to the bottom right of the issue view.

Atlassian haven't coded for it because it should be a rare occurrence.  I want to ask why are your people spending hours editing issues?  It's an issue tracker, not a documentation system.