-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
jira: Use fields in comment to merge in additional data #4304
jira: Use fields in comment to merge in additional data #4304
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for your contribution! Can you please add a changelog fragment? Thanks.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this also be mentioned in the documentation of the fields
option?
Co-authored-by: Felix Fontein <felix@fontein.de>
Oh yes, I added some documentation there. |
recheck |
Co-authored-by: Felix Fontein <felix@fontein.de>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. If nobody complains in say a week, I'll merge this.
hi @Boosai thanks for the contribution. Has this code been tested somewhere? Assuming a yes, it would be nice to have that use case added to the integration tests. |
Hi @russoz, we tested it manually against Jira v8.20.1 with JIRA In order to test this via the module you would need to integrate further functions (2?) to get the property keys & property key values from the api. See https://developer.atlassian.com/cloud/jira/platform/rest/v2/api-group-issue-comment-properties/#api-group-issue-comment-properties What do you think? |
@russoz what do you think? To me it sounds like this should be merged as-is. |
@felixfontein yup, I think we can merge it. |
Backport to stable-4: 💚 backport PR created✅ Backport PR branch: Backported as #4347 🤖 @patchback |
* jira: Use fields in comment to merge in additional data * changlog fragment added * Update changelogs/fragments/4304-jira-fields-in-comment.yml Co-authored-by: Felix Fontein <felix@fontein.de> * updated fields documentation * Update plugins/modules/web_infrastructure/jira.py Co-authored-by: Felix Fontein <felix@fontein.de> Co-authored-by: Felix Fontein <felix@fontein.de> (cherry picked from commit 4fbba96)
* jira: Use fields in comment to merge in additional data * changlog fragment added * Update changelogs/fragments/4304-jira-fields-in-comment.yml Co-authored-by: Felix Fontein <felix@fontein.de> * updated fields documentation * Update plugins/modules/web_infrastructure/jira.py Co-authored-by: Felix Fontein <felix@fontein.de> Co-authored-by: Felix Fontein <felix@fontein.de> (cherry picked from commit 4fbba96) Co-authored-by: Boosai <51994151+Boosai@users.noreply.github.com>
SUMMARY
The 'fields' parameter could be used to merge in any arbitrary data to a jira comment.
ISSUE TYPE
COMPONENT NAME
Enhancement of comment creation in community.general.jira.
ADDITIONAL INFORMATION
In jira issue creation, the 'fields' parameter is used to pass in any arbitrary data.
We adopted this to work also in jira comment creation.
In our jira service desk environment, we use it to set a property to mark the comment as 'internal'.
Look at the example I added.
(Some explanation that helped to find the correct property for this:
https://stackoverflow.com/questions/45031475/how-to-create-an-internal-comment-on-a-jira-issue-using-the-jira-cloud-rest-api )