Can you make a single issue read-only?

[Raj Vora]

Use case:

Lets say I have issue A opened.  Then someone (without knowing issue A is opened) opens up another issue (issue B) which discusses the same problems outlined in issue A.  

Obviously we don't want two duplicate issues since they involve the same problem.  How do I make one of the issues read-only which would force all the discussion about this problem to be in the other issue?

I am aware that there is a way to make an issue read-only based on transition conditions in a customized work flow:

https://community.atlassian.com/t5/Jira-questions/Making-a-closed-issue-read-only/qaq-p/365063

But what I am looking for is a way to do this for a particular issue.  I prefer not to modify workflows that would impact all issues for a particular issue type.  Thanks.

[Brittany Wispell]

Hey @Raj Vora

Have you looked into Issue Level Security? 

Configuring Issue Level Security

You can set this to that specific issue upon creation or edit it. 

You can edit it to where only a specific user can change it. (you'll still need the ability to change it potentially) 

Hope this helps! 

[Tom Hawkins]

Hello @Raj Vora @Brittany Wispell I'm also here because I want to make a single issue read only, but in my case, it's because we have an issue with lots of description and other fields set in a specific way as a template for cloning, and occasionally users edit the original instead of the clone, so my requirement is to be able to limit a specified issue ONLY and not an entire project, issue type or workflow. Configuring Issue Level Security didn't show me a way of doing this, any ideas? 

(PS @Raj Vora we would usually just close one duplicate with a link to the other in your use case by the way)

[Geetha]

Even I'm facing the same issue users are modifying the issue instead of cloning it.