Thank you for you answer!
Do you have any idea how can protect sensitive information in the following situation:
- We got one issue type where users with a specific project role enter information (some of them are classified).
- In a specific step of the workflow the issue typ changes and users with a different project role can now see the issue with this second issue type which hides the classified information.
My problem now is the following:
I noticed that even if the second issue typ hides the classifed information, there is still a possibility to see it, if the first project role had to change this information using the first issue type. Because then this change (of the classifed information) can be found in the history and - like you already said - everyone can see it.
Okay, so instead of changing the issue type you may want to consider creating a new issue and copy over the information that is needed. By doing this you can keep the sensitive data separate and the only the specific users will be able to see the history of the first issue.
“Organizations are made of people who create and follow processes which are constantly changing and are in need to be supported and nurtured… this is the spot where I realized I can br...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event