for now looks like the only way to fix this is to change the default create issue fields in jira then force my developers to create the jira issue then go back and immediately edit the dev only fields in jira, nice enhancement!
should allow different create issues fields for jira and salesforce or turn off showing the review and createe button or setting to only display fields in salesforce that are mapped in the binding
Developers have access to sensitive fields like Sprint and fix versions , Dev Completion Date, High Risk Deployment, etc. and only create in Jira at our company, our support people are the only ones that use salesforce to create Jira issues and they should never have access to Dev only fields.
Aidin Mahmoodi
for now looks like the only way to fix this is to change the default create issue fields in jira then force my developers to create the jira issue then go back and immediately edit the dev only fields in jira, nice enhancement!
Attachments Open full size
should allow different create issues fields for jira and salesforce or turn off showing the review and createe button or setting to only display fields in salesforce that are mapped in the binding
Attachments Open full size
Developers have access to sensitive fields like Sprint and fix versions , Dev Completion Date, High Risk Deployment, etc. and only create in Jira at our company, our support people are the only ones that use salesforce to create Jira issues and they should never have access to Dev only fields.
Attachments Open full size
https://success.servicerocket.com/support/browse/SRSUP-964
Attachments Open full size