-
Notifications
You must be signed in to change notification settings - Fork 4
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
[PAPP-32695] Jira: Bugfix -Adding support for Jira error messages stored in HTTP Response object #30
Merged
Conversation
This file contains 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
bbielinski-splunk
changed the title
Adding support for Jira error messages stored in HTTP Response object
[PAPP-32695] Jira: Bugfix -Adding support for Jira error messages stored in HTTP Response object
Dec 14, 2023
bbielinski-splunk
force-pushed
the
bbielinski/PAPP-32695
branch
from
December 14, 2023 14:33
7b5b9ab
to
c0d2c37
Compare
# Conflicts: # jira.json
bbielinski-splunk
force-pushed
the
bbielinski/PAPP-32695
branch
2 times, most recently
from
February 5, 2024 14:41
edd67d2
to
16e8951
Compare
bbielinski-splunk
force-pushed
the
bbielinski/PAPP-32695
branch
from
February 6, 2024 11:09
16e8951
to
a0b15d3
Compare
bbielinski-splunk
force-pushed
the
bbielinski/PAPP-32695
branch
from
February 12, 2024 11:16
495747e
to
1d4d6db
Compare
mposluszny-splunk
approved these changes
Feb 12, 2024
tonyc-phantom
approved these changes
Feb 12, 2024
bbielinski-splunk
force-pushed
the
bbielinski/PAPP-32695
branch
from
February 19, 2024 10:03
3012248
to
d7a82c3
Compare
bbielinski-splunk
added a commit
that referenced
this pull request
Feb 19, 2024
* [PAPP-32695] Jira: Bugfix -Adding support for Jira error messages stored in HTTP Response object (#30) * Adding support for Jira error messages stored in HTTP Response object * Updating dependencies due to security vulnerabilities * Update README.md * Updating wheel files * Refactoring setting jira error * Clean up for wheel files --------- Co-authored-by: splunk-soar-connectors-admin <admin@splunksoar> * Bumped up the version of jira from 3.7.0 to 3.7.1 * Release notes for version 3.7.1 * Release notes for version 3.7.1 --------- Co-authored-by: bbielinski-splunk <[email protected]> Co-authored-by: splunk-soar-connectors-admin <admin@splunksoar> Co-authored-by: root <root@splunksoar>
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.
Please ensure your pull request (PR) adheres to the following guidelines:
Pull Request Checklist
Please check if your PR fulfills the following requirements:
<App Name>: <PR Type> - <PR Description>
next
branch of the forked repo. Create separate feature branch for raising the PR.Pull Request Type
Please check the type of change your PR introduces:
Security Considerations (REQUIRED)
please document them in the
manual_readme_content.md
.manual_readme_content.md
all methods (eg, OAuth) used to authenticatewith the service that the connector is integrating with.
manual_readme_content.md
.the Vault API.
nosemgrep
?If yes, please provide justification in an additional comment next to the ignored code.
Release Notes (REQUIRED)
What is the current behavior? (OPTIONAL)
n/a
What is the new behavior? (OPTIONAL)
n/a
Other information (OPTIONAL)
n/a
Pay close attention to (OPTIONAL)
n/a
Screenshots (if relevant)
n/a
Thanks for contributing!