Details
-
Suggestion
-
Resolution: Unresolved
-
None
-
None
Description
Hi
Following on from the secret key implementation, which migrated all webhooks to global secret keys and set the name to be the same as the value of the keys itself (in our case several MS Teams webhook connector url's.
Can you please implement the following in future versions:
- Do not set all migrated keys to global, please have them inherit the project restriction the rule they are attached to already has.
- Please allow us to rename the keys from the front end. I would now have to go through over 100 entries in the database across 3 database tables that I've identified, to rename the Key and ensure it continues to work in the rules:
AO_589059_RULE_CFG_COMPONENT.value
AO_589059_RULE_TO_SECRET.key
AO_589059_RULE_SECRET.key
I've tested this method in our dev instance on several rules and I know this method works, however I'd prefer to not have to do this and I'd also prefer to not have to remake all the keys and edit all the rules just to do it from the front end.
I will most likely be holding off upgrading our Automation for Jira version for as long as possible in the hope this gets implemented.
regards