Summary

Automated Processes that update issues without user intervention can be configured with Jira.  If the user that set to perform these updates is used in multiple process, how can it be determined which app is performing an update on an issue? 

Environment

All Jira Server/Data Center versions. 

Solution

There are a few ways to help narrow down what process may be performing the updates: 

• Analyze the commonality of when the behavior is occurring.  For example, are updates occurring upon a specific workflow transition or upon a specific event on an issue? 
  • This can be helpful to understand where to start looking.  If it happens upon a transition, for example, then the workflow transition would be a good place to start investigating. 
• Disable non-essential Marketplace apps and attempt to recreate the behavior.   
  • This can be done by Enabling Safe Mode.  
  • After enabling Safe Mode, if the behavior cannot be replicated, then the apps can be re-enabled one by one to identify the app that is triggering the updates.  
  • If the behavior is still replicated within Safe Mode, then the behavior is likely caused by native functionality.  
• Reviewing the atlassian-jira.log files can provide information to help identify the app that is triggering the behavior.  Searching the logs for the username around the timeframe where an automated change was known to occur may show the Java Class or specific logging contexts that would help identify the app making the changes. 
  • For example: com.atlassian.jira would indicate a native functionality in Jira.