Uploaded image for project: 'Jira Service Management Cloud'
  1. Jira Service Management Cloud
  2. JSDCLOUD-3494

Make the 'customer' available in workflows

XMLWordPrintable

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      NOTE: This suggestion is for JIRA Service Desk Cloud. Using JIRA Service Desk Server? 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.

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

            Matthew Hunter added a comment -
            Atlassian Update - June 1, 2021

            Hi everyone,

            Thank you for bringing this suggestion to our attention.

            As explained in our new feature policy, there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritize and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order.

            Unfortunately, as a result of inactivity (no votes or comments for an extended period of time), this suggestion didn’t make it to the roadmap and we are closing it.

            While this issue has been closed, our Product Managers continue to look at requests in https://jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket.

            Thank you again for providing valuable feedback to our team!

            Matthew Hunter added a comment - Atlassian Update - June 1, 2021 Hi everyone, Thank you for bringing this suggestion to our attention. As explained in our new feature policy , there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritize and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order. Unfortunately, as a result of inactivity (no votes or comments for an extended period of time), this suggestion didn’t make it to the roadmap and we are closing it. While this issue has been closed, our Product Managers continue to look at requests in https://jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket. Thank you again for providing valuable feedback to our team!

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

                Created:
                Updated:
                Resolved: