The basic answer is there are some work arounds like the security scheme, but JIRA doesn't support issue locking at the database level like some tools.
The problem I see with the security scheme work around @Gary Pasquale suggests is if only the assignee can see the ticket it will interfere with reports and project progress views.
Hi Nagaraju,
Sounds like your wishing to stop users editing the ticket at the same time rather than stopping all editing?
One way would be to use an Issue Security Scheme.
Within the scheme, you could have a security level (called whatever you feel is suitable) which restricts visibility of the ticket to the current assignee only.
The default security level will enable visibility of the ticket to all users.
So the process would be: When the engineer picks up the ticket, they assign it to themselves and then changes the security level while they work on/update the issue. Then change the security level back to the default.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Nagaraju,
I think this answer from Nic Brough could help you: https://community.atlassian.com/t5/Jira-Core-questions/is-there-a-way-to-lock-an-issue-so-that-no-one-can-make-further/qaq-p/436348
If you can closer describe, what do you want to achieve, I can try to give you better advice.
Best regards,
Ondra
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.