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

Allowing selected (custom/standard) fields to be updated #158

Open
wants to merge 10 commits into
base: master
Choose a base branch
from

Conversation

MytkoEnko
Copy link

@MytkoEnko MytkoEnko commented Apr 30, 2023

Could anyone please review this pr?

It is backward compatible, as by default it does nothing, only in a way that feature might interfere with the logic of (#150) as it might still update some values even if updateSummary and updateDescription flags are disabled.

If that is ok, I could move these updateSummary, updateDescription and reopenTickets flags to the config to make it more flexible and allow "per-receiver" configs rather than global flags.

Resolves #157

@MytkoEnko MytkoEnko force-pushed the fields_updates_improvement branch 2 times, most recently from 7e8a2f6 to 54ff2a7 Compare April 30, 2023 15:12
@MytkoEnko MytkoEnko changed the title Allowing selected (custom/standard) fields to be updated resolves #157 Allowing selected (custom/standard) fields to be updated Apr 30, 2023
Copy link
Member

@bwplotka bwplotka left a comment

Choose a reason for hiding this comment

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

Nice, I don't have full context on the use case, but feels like a useful logic. Added some suggestions. Thanks, sorry for lag.

pkg/notify/notify.go Outdated Show resolved Hide resolved
pkg/notify/notify.go Outdated Show resolved Hide resolved
pkg/notify/notify.go Outdated Show resolved Hide resolved
pkg/config/config.go Outdated Show resolved Hide resolved
MytkoEnko and others added 7 commits February 6, 2024 20:07
Signed-off-by: MytkoEnko <deass@ukr.net>
Signed-off-by: MytkoEnko <deass@ukr.net>
Signed-off-by: MytkoEnko <deass@ukr.net>
Co-authored-by: Bartlomiej Plotka <bwplotka@gmail.com>
Signed-off-by: Dmytro Aleksieiev <deass@ukr.net>
Co-authored-by: Bartlomiej Plotka <bwplotka@gmail.com>
Signed-off-by: Dmytro Aleksieiev <deass@ukr.net>
Co-authored-by: Bartlomiej Plotka <bwplotka@gmail.com>
Signed-off-by: Dmytro Aleksieiev <deass@ukr.net>
Co-authored-by: Bartlomiej Plotka <bwplotka@gmail.com>
Signed-off-by: Dmytro Aleksieiev <deass@ukr.net>
Signed-off-by: Dmytro Aleksieiev <deass@ukr.net>
@MytkoEnko
Copy link
Author

@bwplotka Thanks for he review! Applied suggestions and rebased.

In our organisation we've mapped alert's $value to an annotation and wanted corresponding jira field to be always up to date as it was important for prioritizing similar alert tickets.
But it could be also useful in other cases where fields mapped to label/annotation for new or reopened tickets would reflect the change. For example if we add a new label to an existing alert and map it to a field.

Copy link
Member

@bwplotka bwplotka left a comment

Choose a reason for hiding this comment

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

👍🏽 Thanks

pkg/config/config_test.go Outdated Show resolved Hide resolved
MytkoEnko and others added 2 commits February 7, 2024 11:46
Co-authored-by: Bartlomiej Plotka <bwplotka@gmail.com>
Signed-off-by: Dmytro Aleksieiev <deass@ukr.net>
Signed-off-by: Dmytro Aleksieiev <deass@ukr.net>
@MytkoEnko
Copy link
Author

Ready to be merged.

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.

Allow selected (custom/standard) fields to be updated
2 participants