Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-3494

Make the 'customer' available in workflows

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Low Engagement
    • None
    • Automation
    • None
    • We collect Jira Service Desk feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding suggestion.

      At the moment there are is the Actions add-on which makes it possible to display transitions on a portal. The add-on has to be configured with a "Technical User" who is a JIRA user and will execute the transition, regardless of who is logged in to the portal.

      In my workflow I have transitions with various custom conditions, validators and post-functions (provided by add-ons, script runner scripts, developed ourselves, ...). However, it does not seem possible to figure out who is actually logged in in the portal and do something with that info.

      In the code snippet below, both the loggedInUser and caller will refer to the "Technical User". 

      ApplicationUser loggedInUser = ComponentAccessor.getJiraAuthenticationContext().getUser()

String caller = ((WorkflowContext) transientVars.get("context")).getCaller();

      For postfunctions, for example, a simple solution could be to add "portalUser" to "transientVars". Then it can be accessed via:

      String portalUser = transientVars.get("portalUser")

      I noticed that work on JSD-40 has started, but I'm not sure if that will also cover this suggestion.

          Form Name

            [JSDSERVER-3494] Make the 'customer' available in workflows

            Charlie Marriott added a comment -
            Atlassian Update – 1 March 2021

            Hi,

            Thank you for raising and watching this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request.

            This is an automated update triggered by low engagement with this suggestion (number of votes, number of watchers).

            We hope you will appreciate our candid communication and our attempts to become more transparent about our priorities. You can read more about our approach to highly voted suggestions here, and how we prioritise what to implement here.

            To learn more about our recent investments in Jira Service Management and Data Center, please check our public roadmap and our two dashboards containing recently resolved issues, and current work and future plans.

            Regards,

            Jira Service Management, Server & Data Center

            Charlie Marriott added a comment - Atlassian Update – 1 March 2021 Hi, Thank you for raising and watching this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request. This is an automated update triggered by low engagement with this suggestion (number of votes, number of watchers). We hope you will appreciate our candid communication and our attempts to become more transparent about our priorities. You can read more about our approach to highly voted suggestions here , and how we prioritise what to implement here . To learn more about our recent investments in Jira Service Management and Data Center, please check our public roadmap and our two dashboards containing recently resolved issues , and current work and future plans . Regards, Jira Service Management, Server & Data Center

              Unassigned Unassigned
              01ee0bbd8676 Glenn Verrijkt
              Votes:
              2 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: