Skip to end of banner
Go to start of banner

How to get problem determination information

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

If things are not working as expected, it can often be resolved by being careful with the configuration and looking at errors produced. Some time more detailed problem determination information may need to be sent in. 

 

Look at other tips

See Tips.

Initial Steps

  1. How to add advanced logging is strongly recommended.
  2. Double check your configuration together with looking at various how to's. 
  3. Look through your server log for entries indicating various problems that can occur during a transition. The log is the only place some of these errors can be reported. This is especially true for problems with custom fields. Error entries are logged for most situations that cannot be completed as expected. A post function runs after the transition has occurred, so error logs are really the best way to indicate that some things may not have done based on the situation.
  4. If still a problem, open an issue with information on your configuration, Confluence version, and plugin version. 
  5. In most cases, that will be sufficient to resolve the issue. In some situation more information may be needed. For instance you can attach your exported workflow. In more difficult cases, you may be instructed to collect debug information. These are the steps to follow. You will need access to the JIRA server log file. 

Look for lines in the server log with .acli.

 

Steps to collection debug information

  1. Read: JIRA logging and profiling - how to configure additional temporary logging in JIRA
  2. Add an entry for DEBUG using org.swift.jira.acli
    • Temporary logging will get you started without a server restart. It does not carry over after restart.
  3. Run a test scenario and then look in the server log. Find the time period close to your test run time and look for entries including text: org.swift.jira.acli.
  4. Attach one of the following
    1. Cut and paste the entries into a comment (if small) or into a file and attach
    2. Zip of your server log - make sure it doesn't contain sensitive information
    3. Copy your server log and remove earlier entries or other information you may not want to share.
  • No labels

Log a request with our support team.

Confluence®, Jira®, Atlassian Bamboo®, Bitbucket®, Fisheye®, and Atlassian Crucible® are registered trademarks of Atlassian®
Copyright © 2005 - 2024 Appfire | All rights reserved. Appfire™, the 'Apps for makers™' slogan and Bob Swift Atlassian Apps™ are all trademarks of Appfire Technologies, LLC.