Feature Needed: Jira Issue Lock

[Mark Murawski]

We still use Jira Server and we've been avoiding moving to jira cloud because of a major major functional loss.

We use this addon
Issue Lock for Jira (who's editing)
https://marketplace.atlassian.com/apps/1214307/issue-lock-for-jira-whos-editing?tab=overview&hosting=datacenter

But this is not available for cloud.

Please add this feature so we can migrate to cloud.

[Mark Murawski]

My thought is to develop a tampermonkey addon to accomplish this.  (The problem would be, it only works for PC, so mobile users could still 'sneak into' an issue).

There does exist a 'Who is looking' plugin/addon for Jira cloud, but it does not support actually locking the issue.

I think this might be able to be accomplished by a hodgepodge of automation... write a custom addon that will add a custom field to the issue of the current user. 
- And then add workflow steps at each workflow transition to block transition if the current user doesn't match the 'locked' user custom-field
- And then upon issue comment, block new comments using the same rules as above (I'm not actually sure if you can use an automation rule to add a comment)
- And then,  would possibly need a cron job to expire out old locks if someone's not been on the issue for a time period

[Kai Becker]

Hi @Mark Murawski 

sorry to say but this app will never be available in the marketplace for cloud. The problem is that the technology stack is completely different between Server/DC and Cloud.
It is not possible to develop such an app for cloud. 

We have a few customers that use this/or corresponding apps and I had a lot of discussions about that because of migrating to cloud.

[John Funk]

Hi Mark - What exactly does the app do that you need to happen in Jira Cloud?

[Mark Murawski]

Hi John,

It locks the issue temporarily if someone is working on it.

- Tech views issue -- first user to get to the issue 'wins'
- Tech automatically locks the issue, preventing status changes or comments until the tech is off the issue page
- Other users can see who is also on the issue
- Admin/Manager can steal the lock to take over the issue

[John Funk]

You can probably do this by setting properties on the transitions to prevent editing. 

https://support.atlassian.com/jira-cloud-administration/docs/use-workflow-properties/

Then you can add self looping transitions on the status that has conditions so that only certain people can execute the transitions which would then set or open up the editing. 

It's a bit of work and a workaround, but you can probably do it. That thing alone should not keep you from migrating.