• 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 Cloud. Using JIRA Server? See the corresponding suggestion.

      We have implemented a SOAP API that will cause Perforce triggers to push work-logs and state transitions on JIRA. The problem is that we're doing this with a dummy SOAP user (trigger-user) to accomplish these SOAP calls.

      There should be a way to allow that dummy SOAP user (which contains admin privileges) to login and execute SOAP commands on behalf of a user that way the work-log and state transitions being made can be tracked as the user as oppose to the dummy user.

            [JRACLOUD-17812] SOAP & XML-RPC "login as" a given user

            Dave Meyer added a comment -

            JIRA's SOAP API was deprecated in JIRA 6.0 and will be removed in JIRA 7.0. This is supported in the JIRA REST API.

            Dave Meyer added a comment - JIRA's SOAP API was deprecated in JIRA 6.0 and will be removed in JIRA 7.0. This is supported in the JIRA REST API.

            AntonA added a comment -

            Hi Tim,

            Thanks for the clarification. I missed the UI/SOAP difference.

            I will leave this issue open. For more information on the way new feature and improvement requests are scheduled, please see:
            http://confluence.atlassian.com/display/DEV/Implementation+of+New+Features+and+Improvements

            Cheers,
            Anton

            AntonA added a comment - Hi Tim, Thanks for the clarification. I missed the UI/SOAP difference. I will leave this issue open. For more information on the way new feature and improvement requests are scheduled, please see: http://confluence.atlassian.com/display/DEV/Implementation+of+New+Features+and+Improvements Cheers, Anton

            If I am wrong about this, could you please tell me how this request is different from JRA-2134?

            This is totally different in a sense that JRA-2134 is trying to address SU like capabilities from the GUI. This improvement however is talking about enhancing JIRA's SOAP API such that a new soap function called login_as() is implemented. The new function will inherit the existing soap login() call but will take a third argument as the user we wish to login as.

            The workaround plugin discussed in JRA-2134's comment does not address the SOAP piece of the requested improvement. Please re-open the issue; let me know should you need further clarification...

            Tim Kaddoura added a comment - If I am wrong about this, could you please tell me how this request is different from JRA-2134 ? This is totally different in a sense that JRA-2134 is trying to address SU like capabilities from the GUI. This improvement however is talking about enhancing JIRA's SOAP API such that a new soap function called login_as() is implemented. The new function will inherit the existing soap login() call but will take a third argument as the user we wish to login as. The workaround plugin discussed in JRA-2134's comment does not address the SOAP piece of the requested improvement. Please re-open the issue; let me know should you need further clarification...

            AntonA added a comment -

            Hi Tim,

            This appears to be a duplicate of JRA-2134 and therefore I will resolve this issue.

            If I am wrong about this, could you please tell me how this request is different from JRA-2134?

            Cheers,
            Anton

            AntonA added a comment - Hi Tim, This appears to be a duplicate of JRA-2134 and therefore I will resolve this issue. If I am wrong about this, could you please tell me how this request is different from JRA-2134 ? Cheers, Anton

              Unassigned Unassigned
              131295ceaac3 Tim Kaddoura
              Votes:
              3 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: