BDMS-557-Implement-a-GitHub-Action-that-automatically-creates-a-corresponding-Jira-issue-whenever-a-new-GitHub-Issue-is-opened-in-selected-repositories#516
Merged
Conversation
jirhiker
deleted the
BDMS-557-Implement-a-GitHub-Action-that-automatically-creates-a-corresponding-Jira-issue-whenever-a-new-GitHub-Issue-is-opened-in-selected-repositories
branch
Contributor
There was a problem hiding this comment.
Pull request overview
This PR fixes a bug in the GitHub Actions workflow that creates Jira issues from GitHub issues. The issue was that newlines in the Jira description were being escaped incorrectly, causing literal \n characters to appear in the description instead of actual line breaks.
Changes:
- Fixed string escaping in the Jira description format by changing
\\nto\non lines 116-117
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
This PR addresses the following problem / context:
How
Implementation summary - the following was changed / added / removed:
Notes
Any special considerations, workarounds, or follow-up work to note?