You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Join now to unlock these features and more
Hello, Again, Community:
My question this time has to do with automation rules and Jira issue History. I have developed an automation scheme to detect Jira issues that spend more than a predefined number of workdays in each status column. This scheme executes two different automation rule-sets five nights a week. Each rule-set generates an entry into each issue History. After even just a few nights of rule execution, the issue History gets cluttered to the point where it is impossible to find relevant info about the issue.
Is there a way to prevent/block automation rules from writing to issue history?
My continued "Thanks" for this community's generous and helpful knowledge.
BTW...We're using Team-Managed Kanban.
What actions are the Automation Rules performing that are resulting in entries in Issue History? If they are making some sort of modification to the issues, why would you want to exclude that from the events written in the issue history?
IMO it would be a bad idea to be able to exclude events or actors from generating Issue History entries, and this compromises your ability to audit what happens on an issue.
Hello, @Trudy Claspill :
Thanks for the response. The automation rules do change the issues by updating custom fields specific to monitoring time-in-status and indicating those issues that remain in a given status beyond a pre-set number of workdays.
I completely understand your advice about an "audit trail". The History entries are specific to time-in-status; they have no relevance to the issue's development-related activities; the issue assignee has no interest in the time-in-status logging specifics. They, and management, only needs to know that a given issue is "stuck".
The automation rules write necessary information into the automation log file, so I have audit/debug traceability. Consequently, I believe that there is minimum risk in omitting these automation events from the issue History.