Ability to limit the number of associations between Jira Issue & Salesforce object
Currently it's not possible to limit the number of associations. We would like to have a one-to-one association between Jira issues and Salesforce objects.
This feature would be very useful for our workflow as well. We currently use our integration to track customer work being done in Jira (managed by our development teams) to Accounts in Salesforce for our customer success managers to be able to visualize what is in progress.
We use a custom object in Salesforce to link the Jira issue to that object and it should be a 1:1 relationship. Currently, as the process is new, users are duplicating the objects in Salesforce creating a 1:Many relationship which breaks our integration further down the road.
Being able to restrict this, both to avoid human error and just to ensure data integrity would be extremely useful.
This feature would be very useful for our workflow as well. We currently use our integration to track customer work being done in Jira (managed by our development teams) to Accounts in Salesforce for our customer success managers to be able to visualize what is in progress.
We use a custom object in Salesforce to link the Jira issue to that object and it should be a 1:1 relationship. Currently, as the process is new, users are duplicating the objects in Salesforce creating a 1:Many relationship which breaks our integration further down the road.
Being able to restrict this, both to avoid human error and just to ensure data integrity would be extremely useful.
Attachments Open full size