Error formatting macro: appfire-confluence-analytics: java.lang.NullPointerException: Cannot invoke "com.atlassian.confluence.xhtml.api.MacroDefinition.getMacroId()" because "macroDefinition" is null
Skip to end of banner
Go to start of banner

Debug condition configurations

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Description

Conditioning allows for flexibility in determining for creating an issue, but ensuring that it works as intended is a tricky process.

  • Ensure that you have tested your regex and it behaves exactly the way you want it to, using a regex testing tool like RegexPlanet or a similar tool.
  • Make sure that the data value you provide, produces the expected value.

The only way to verify the above checks is through adding additional logging in the JIRA server log. You need a JIRA administrator access to view the log in your <home>/log directory.

Steps

  1. Read JIRA logging and profiling to know how to configure additional temporary logging in JIRA.
  2. Add an entry for INFO using org.swift.jira
    • Temporary logging helps you to get started without a server restart.
    • Consider adding a permanent entry to resolve issues that occur in production.
  3. Run a test scenario and then look in the server log and look for entries including text: Condition value: or similar entries.

More Information

Additional problem determination information is available from Retrieve problem determination information.


  • No labels