We only want the associate and not the create it concerns our salesforce admins that anyone with edit access ot the project tickets would be able to create random SF objects : )
we have the same situation where issues should be coming from our CS reps and SF so we don't need those buttons. Would like to be able to hide them, similar to how that's done on the SF side.
We only want the associate and not the create it concerns our salesforce admins that anyone with edit access ot the project tickets would be able to create random SF objects : )
Attachments Open full size
we have the same situation where issues should be coming from our CS reps and SF so we don't need those buttons. Would like to be able to hide them, similar to how that's done on the SF side.
Attachments Open full size
As a workaround the following snippet can be added to the announcement banner:
<script>
require(['aui/banner'], function (banner) {
banner({
body: 'DEV-System || Abzug von Produktion vom 20.01.2020 || DEV-System'
});
});
$('document').ready(function(){
if (jQuery("#sf-issue-overview-panel_heading").length>0){
let waitForSalesForcePanel = () => {
const container = jQuery("#sfjp-iframe").contents().find("style")[0];
if (!container) {
setTimeout(waitForSalesForcePanel , 50);
} else {
var head = jQuery("#sfjp-iframe").contents().find("head");
var css = '<style type="text/css">' +
'#sf-issue-overview-header {display:none}; ' +
'</style>';
jQuery(head).append(css);
}
};
waitForSalesForcePanel();
}
});
</script>
Attachments Open full size
https://servicerocket-community.force.com/atlassian/s/question/0D5A0000032PwtnKAC/sf-cant-see-jira-attachment-when-jira-is-modificationdisabled-to-prevent-sf-case-creation?t=1522214971940
Attachments Open full size
A customer wanted to only hide the create button in Jira.
Can we do it like the Salesforce Package? eg. feature toggles?
https://success.servicerocket.com/support/browse/SRSUP-397
Attachments Open full size
One way is to remove the Edit permission on the project, but this affects other edit operations to the Jira issue.
Attachments Open full size