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

[twotired]

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]

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)

[mattb18]

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]

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?