# The form data below was edited by perforce # Perforce Workshop Jobs # # Job: The job name. 'new' generates a sequenced job number. # # Status: Job status; required field. There is no enforced or # promoted workflow for transition of jobs from one # status to another, just a set of job status values # for users to apply as they see fit. Possible values: # # open - Issue is available to be worked on. # # inprogress - Active development is in progress. # # blocked - Issue cannot be implemented for some reason. # # fixed - Fixed, optional status to use before closed. # # closed - Issue has been dealt with definitively. # # punted - Decision made not to address the issue, # possibly not ever. # # suspended - Decision made not to address the issue # in the immediate future, but noting that it may # have some merit and may be revisited later. # # duplicate - Duplicate of another issue that. # # obsolete - The need behind the request has become # overcome by events. # # Project: The project this job is for. Required. # # Severity: [A/B/C] (A is highest) Required. # # ReportedBy The user who created the job. Can be changed. # # ReportedDate: The date the job was created. Automatic. # # ModifiedBy: The user who last modified this job. Automatic. # # ModifiedDate: The date this job was last modified. Automatic. # # OwnedBy: The owner, responsible for doing the job. Optional. # # Description: Description of the job. Required. # # DevNotes: Developer's comments. Optional. Can be used to # explain a status, e.g. for blocked, punted, # obsolete or duplicate jobs. May also provide # additional information such as the earliest release # in which a bug is known to exist. # # Component: Projects may use this optional field to indicate # which component of the project a givenjob is associated # with. # # For the SDP, the list of components is defined in: # //guest/perforce_software/sdp/tools/components.txt # # Type: Type of job [Bug/Feature]. Required. # # Release: Release in which job is intended to be fixed. Job: job000478 Status: closed Project: perforce_software-slack Severity: A ReportedBy: thomas_gray ReportedDate: 2016/03/08 09:09:34 ModifiedBy: perforce ModifiedDate: 2019/02/19 10:51:31 OwnedBy: thomas_gray Description: From user @rtande on the forums: (http://forums.perforce.com/index.php?/topic/4693-slack-integration-for-swarm/) I'm trying the Slack integration for Swarm and I think I have everything setup correctly. I'm using the instructions from https://swarm.worksh...software-slack/ but I'm not seeing anything in the Slack channel that I've created to receive updates from Swarm. I've done the following - copied across the files mentioned in the instructions to the relevant locations in my Swarm install - changed the file permissions on the files and directories to ensure that they are writeable and executable as required - set up the webhook in my Slack channel - copied that webhook into the settings for the Swarm project that I'm using I don't see any error messages in my Swarm error log or any POSTs from Swarm to the Slack webhook URL in my Swarm access log. Any help or pointers gratefully accepted. DevNotes: Type: Bug