Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FX-4604] Allow updating External Ticket References #271

Merged
merged 1 commit into from
Dec 18, 2024

Conversation

grayson-cobalt
Copy link
Collaborator

No description provided.

Copy link

netlify bot commented Dec 17, 2024

Deploy Preview for cobalt-public-api ready!

Name Link
🔨 Latest commit 2192bb6
🔍 Latest deploy log https://app.netlify.com/sites/cobalt-public-api/deploys/6761fde59da16100080e8876
😎 Deploy Preview https://deploy-preview-271--cobalt-public-api.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@grayson-cobalt grayson-cobalt marked this pull request as ready for review December 17, 2024 22:47
@grayson-cobalt grayson-cobalt requested a review from a team as a code owner December 17, 2024 22:47
"ticketing_system": "jira",
"external_url": "https://my-project.atlassian.net/browse/TEST-37",
"external_id": "10214",
"finding_id": "vl_JTovzf8AW1afCRpKJejse3"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah we do. It's intentionally omitted from the documentation so that we can remove it later.

Context:
We initially called the functionality "External Finding References" (you'll still find this name in lots of the code).
Before we released (documented) these public API routes, we thought about it again and decided that the name "External Ticket Reference" made a lot more sense, so we released the API routes under that name. As part of that renaming, we also added the ticketing_system property that has the same value as reference_type. reference_type was still exposed because it was used by early workato recipes that were in use by a small handful of customers. The idea is to remove the duplicate (undocumented) API routes with the name /external_finding_references and remove the reference_type property sometime soon-ish.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

After thinking about it some more, I should probably add an explicit note to the docs telling customers not to use the referenceType property because it will be removed. That could be a follow up PR tho

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for explaining.

@grayson-cobalt grayson-cobalt merged commit 50d636d into main Dec 18, 2024
15 checks passed
@grayson-cobalt grayson-cobalt deleted the chore/FX-4604/edit-etrs branch December 18, 2024 13:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants