JIRA Integration Issues

Users are mapped to their own accounts when using Trusted Applications.

If you (or the general account used for Jira access, if not using Trusted Applications) do not have the permissions to carry out the Jira actions linked from Crucible, an error will occur. Depending on the error returned from Jira, Crucible may not display the error correctly or display it at all, simply reporting that "An error has occurred". To investigate what the error was, you can access the Crucible debug log, named fisheye-debug.log.YYYY-MM-DD under the dist.inst/var/log folder of your Crucible installation. In the debug log, look for the date and time when your error took place. Here, you will be able to follow the links and see what error the Jira instance was producing by clicking through to Jira.

If you are using Jira 4.0 you will not be able to create subtasks in versions of Crucible prior to 2.0.5. If you are affected by this bug, please upgrade to at least 2.0.6 (2.0.5 is affected by another bug CRUC-2471).