You would need three things:
Just be careful with the notifications. Imagine an issue is transitioned to the secret status, triggering an email to an external contractor who happens to be watcher, reporter, assignee or whatever. That person clicks on the link in the email and gets sent to an "access denied" screen. If that's a scenario that bothers you, you can avoid firing the usual generic event in that transition, and fire a custom event instead that notifies different people.
Hi Nicholas – thanks for your suggestion. Couple clarification questions:
1.) By security scheme, do you mean a custom field for Private/External, a Permission scheme, or Issue Security Scheme or combination of more than one?
2.) “add a post-function that sets the Security value to Private”. Seems like the only post functions available are to set values for global JIRA fields, not custom fields. What am I missing.
Thank you for advice.
Atlassian released a security advisory on 3/20/2019. The full advisory is here: https://confluence.atlassian.com/doc/confluence-security-advisory-2019-03-20-966660264.html In a nutshe...
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