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.

Sign up for GitHub

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

Jump to bottom

Store Alert hash in a field other than labels, make it configurable #164

Open
twotired opened this issue May 9, 2023 · 3 comments · May be fixed by #189
Open

Store Alert hash in a field other than labels, make it configurable #164

twotired opened this issue May 9, 2023 · 3 comments · May be fixed by #189

Comments

@twotired
Copy link
Contributor

twotired commented May 9, 2023

It should be possible to configure JIRAlert to store the hash in a different field like, Description or a Comment. When the hash is stored in a Label, that can interfere with existing filters and workflows that depend on labels to report on issues over time.

Would Description be the most performant and versitile alternative, even though full text search would be required?

Shorter hashes would also help de-clutter.
@k0ste
Copy link

k0ste commented May 10, 2023

Would Description be the most performant and versitile alternative, even though full text search would be required?

I think this bad idea. Because description is a field for a template engine. The best alternative solution will be configurable custom_field (type: string, I believe)

This was referenced Nov 18, 2023
Open
Merged
@mattb18
Copy link

mattb18 commented Jan 21, 2024

I'd also be interested in being able to set a custom_field to store the hash. Having a long SHA256 hash in the labels looks pretty messy, it would be good to set this value on a hidden field.

@cropalato
Copy link

cropalato commented May 27, 2024 •
edited
Loading

I have the same problem and will work on a patch for that.
Checking the code I can see "Labels" field is an array including staticLabels, issueGroupLabel, and possibly some other labels.
I know those are labels, but I am facing some problems defining a key name for use in the config file to customize that. Any suggestion?

This was referenced May 28, 2024
Closed
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
4 participants
@twotired @cropalato @k0ste @mattb18