38 Vote

As a User, I want the Default preset (After create/associate) works with Apex Trigger

As a User, I want the Default preset (After create/associate) works with Apex Trigger.

This will help the user able to pull Jira key from Jira after Jira issue automatically create upon Salesforce Case record creation

  • Kevin Lew
  • Sep 12 2019
  • Likely to implement
Hosting platform Cloud, Server
  • Attach files
  • Alexander MacDonald commented
    26 Jul 04:11pm

    We really need this as well. I was under the impression that this would work and is why we have even been working with the Apex Trigger to set a Default preset for Create issues. This is needed to Create a Main issue that is a Mastercase and would be automatically set to Auto-Push and Auto-Pull so that the Jira issue will always keep the SFDC case up to date on status. Any case that is Associated to a Jira case will be consider a Duplicate issue and we are only looking for Jira to Auto-Push the Mastercase status and updates to all SFDC cases. This allows the Mastercase SFDC case and Jira issue to always be in sync but allow all Duplicate SFDC cases to see that status w/o affecting the Jira Mastercase.

  • Shahin Uddin commented
    11 Nov, 2021 04:19pm

    We require this urgently as we have various teams that may move issues across Projects.

    Example: When moving an issue (ABC-123) to another project in Jira, the Jira component in Salesforce updates to show the newly-moved issue (ABC-123 becomes DEF-456), however the mapped field which holds the Jira Key value (e.g ABC-123) does not update (and retains the old key of ABC-123) unless you manually navigate to the Jira tab and click on Pull. There should be a way to pull the Jira Key from Salesforce again when moving across projects.

  • Gerald Gillespie commented
    3 Jun, 2021 09:11am

    I was just told that this was "expected behaviour".

    Expected behaviour ?

    Expected behaviour means that you

    can draw a line between expectations set and behaviour established.

    So please show me where this is expected ( per documentation or per industry norms, whatever you have got). I scanned the documentation and could not find anything in the admin guide nor in the known issues guides / FAQ. if it is not in the documentation then you have a documentation bug.

    So it feels like you have sold me some good-looking fruit, but turns out there is some rot in it. Hoping I am wrong here.

    Assuming there is a bit of bruise here (again forgive me if you have it but i haven't been able to find it) by intuition I would suggest that this should be a bug not a feature request, some say it is semantics, but I suggest that your documentation (or lack of addressing the expectation) and the app nature itself creates and expectation that all your customers may have
    an "idea" which is when it is clear that your product does not have (again, docs and app usage and feature lists) it ...yet...but it could have it. Further, it correlates to a need that many customers foresee. It's potentially even low-hanging fruit for you to pick and provide for those who got the bad fruit.

    More specifically to this "idea".

    "auto"means the

    automation of something that was other-wise manual. Not a new function, but an existing function that can be trusted to be executed when conditions of the process are met.

    please make auto-push do what is expected of push -- except for it to be automatic.

    In the meantime I am going to use Innovalog's JMWE events to trigger this sync (cuz they are awesome) automatically

  • Karol Macák commented
    15 Jan, 2021 02:30pm

    I believe this should be included in package, or even better give parameters for trigger to be able to set it as we need.

  • Kseniya Khenkina commented
    24 Sep, 2020 07:59pm

    This would be fantastic as we use a custom Apex trigger to create new issues in Jira and would love to have the Jira fields synced back after the issues is created, similar to how it works if we use the "create" button on the standard component!

  • Dennis Scholz commented
    22 Jul, 2020 11:11am

    This is a must have feature for our implementation because we use a custom component to create Jira Issue Tickets.

  • Will Adams commented
    19 Feb, 2020 10:51pm

    While from a development point this might be the expected behavior of the call as an end user I would safely classify this as a bug. The expected behavior of the integration would be to automatically push the information back to Salesforce if the set-up is for Auto-Push to be enabled. It should not matter how the Jira issue is created, whether it be manually or through an Apex Trigger.

  • Thomas Nieman commented
    27 Nov, 2019 01:53pm

    We have several projects that have Jira Issues automatically created by a trigger in Salesforce.  If you manually create a Jira Issue from Salesforce the Jira Key does automatically pull from Jira to Salesforce.  It would be great if an API created Jira Issues could sync after creation.


    I would like to see this implemented as a new function or a True/False variable that is passed to the create function that would fire whatever is setup in the Connection.

  • +23