I feel like I've looked everywhere to resolve this on my own, but am hoping someone will point me to something fairly easy that I've overlooked. Here's the situation...
In my project:
Yet, when a user with the restricted role creates an issue, the Linked Issues field is visible and allows them to make changes. Validation prevents anything they do from being saved, but I don't understand why the field even appears, especially since other restricted fields - such as Security Level and Assignee - do not appear.
I'm sure I'm missing something. Can anyone point me in the right direction?
It seems that the situation that you are currently facing has bump into this bug report: https://jira.atlassian.com/browse/JRA-25305
Please feel free to vote on it to increase its popularity and don't forget to add yourself as watcher to receive any latest updates from the developer and feedback from other users that is facing the same problem as well.
Thanks for note, Daryl... However, there is a key difference -- the user in my situation does NOT have Edit Issue permission... I did end up posting my concern as an Atlassian support ticket, and they are trying to recreate it. So, it looks like I'm in a wait and see situation... I'll need to figure out some sort of workaround.
Hello, Community! My name is Gosia and I'm a Product Manager on Jira Server and Data Center here at Atlassian. Since 2002 when we launched our public issue tracker, jira.atlass...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs