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

Use filter to set the common attributes of the events

    XMLWordPrintable

Details

    Description

      JENKINS-54637 has made it easier for the common attributes of the context to be set. As it was implemented and merged recently, few common attributes can be set and managed in the filter.

      This improvement has to be made to the code.

      Attachments

        Activity

          mide David Olorundare added a comment - - edited

          gayathriirajendar This is not a bug. Please fill out a proper description for this and don't just leave it empty. You can take a look at other Jenkins issues in Jira related to the project, to see the correct formatting for newly created issues.

          Item tasks on the Board in the `To Do` pile do not get assigned to someone until they are moved to the `In Progress` list. So either move this task into the `In Progress` pile if you are working on it otherwise set the Assignee to `Unassigned`

          mide David Olorundare added a comment - - edited gayathriirajendar This is not a bug. Please fill out a proper description for this and don't just leave it empty. You can take a look at other Jenkins issues in Jira related to the project, to see the correct formatting for newly created issues. Item tasks on the Board in the `To Do` pile do not get assigned to someone until they are moved to the `In Progress` list. So either move this task into the `In Progress` pile if you are working on it otherwise set the Assignee to `Unassigned`

          Thanks. While creating the issue, it automatically got assinged to you. Sorry for that.

          gayathriirajendar Gayathri Rajendar added a comment - Thanks. While creating the issue, it automatically got assinged to you. Sorry for that.
          mide David Olorundare added a comment - - edited

          Could you rewrite this description. Just writing something was "implemented and merged recently" is not helpful to someone reviewing this ticket in future and trying to trace this back to the code. Outline the problem and state the task(s) that should be done if it is an improvement; not just writing an "improvement has to be made to the code".

          Also, update the issue's "Labels" field with 'audit-logging', not just only 'newbie-friendly'.

          Look at other previously created Jenkins jira issues for examples.

          mide David Olorundare added a comment - - edited Could you rewrite this description. Just writing something was "implemented and merged recently" is not helpful to someone reviewing this ticket in future and trying to trace this back to the code. Outline the problem and state the task(s) that should be done if it is an improvement; not just writing an "improvement has to be made to the code". Also, update the issue's "Labels" field with 'audit-logging', not just only 'newbie-friendly'. Look at other previously created Jenkins jira issues for examples.

          People

            gayathriirajendar Gayathri Rajendar
            gayathriirajendar Gayathri Rajendar
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: