Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-45478

Add support for utm_ query parameters

    XMLWordPrintable

    Details

    • Epic Link:
    • Sprint:
      Blue Ocean 1.2-beta3
    • Similar Issues:
    • Released As:
      2.3.0

      Description

      User story

      As a Jenkins administrator, I would like all the URLs generated by Jenkins for publishing outside of the website to include utm tracking query parameters so that I can measure how my users interact with Jenkins.

      Specifically, I would like to know:

      • How many users respond to the emails generated by Jenkins
      • How many users respond to the instant messaging notifications from Jenkins
      • How many users respond to custom notifications generated by the build script using the RUN_DISPLAY_URL, RUN_CHANGES_DISPLAY_URL or JOB_DISPLAY_URL environment variables.

      Acceptance criteria

      • The Environment Contributor in the Display URL plugin injects utm_source=jenkins&utm_medium=build-environment into its environment variables
      • The DisplayURLProvider.get() api entry point has been deprecated in favour of an entry point that takes the utm_medium as a parameter. The deprecated entry point's behaviour will remain unchanged.
      • There is a new api entry point that takes the utm_medium as a parameter, this entry point will return URLs containing the configured UTM tracking information

        Attachments

          Activity

          Hide
          stephenconnolly Stephen Connolly added a comment -

          Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA

          Show
          stephenconnolly Stephen Connolly added a comment - Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA

            People

            • Assignee:
              stephenconnolly Stephen Connolly
              Reporter:
              stephenconnolly Stephen Connolly
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: