search

cdevents / spec

A common specification for Continuous Delivery events
Apache License 2.0
125 stars 22 forks source link

Define events for tickets/issues #164

Closed sbrennan4 closed 3 months ago

sbrennan4 commented 10 months ago

I'm interested in sending ticket-related events (feature request, bug fix, etc.) to CDEvents. I have two potential use cases in mind:

  1. Observability and metrics. These events could be used to trace a deployment all the way back to the issue that spawned it. They could also help to provide insights such as how long it takes to get from request to implementation.
  2. Interoperability. For regulatory reasons, some of our applications require us to capture product approval prior to releasing to production. We capture these approvals in Jira. If we can link an artifact back to an issue then we can use the approval events from Jira to signal to the CD system that it is okay to release that artifact to production.

Additional Context: This issue is related to discussions in https://github.com/cdevents/spec/issues/59 and this HackMD document regarding incident events.

e-backmark-ericsson commented 9 months ago

Thanks for your suggestion @sbrennan4 ! I agree to the need of ticket-related events. We'll discuss these in one of our coming CDEvents workgroup meetings, so please come there to help us detail this proposal.

afrittoli commented 3 months ago

@sbrennan4 @xibz can this be closed now that #180 is merged?