Error creating subtask in JIRA: Unknown error creating subtask for issue ABC-1234: null

お困りですか?

アトラシアン コミュニティをご利用ください。

コミュニティに質問

症状

When trying to create a sub-task in JIRA from a Crucible review, the following error is thrown:

2011-09-12 18:24:35,981 WARN  [btpool0-581 ] fisheye.app LinkCommentIssueAjaxAction-execute - Error creating subtask in JIRA: Unknown error creating subtask for issue ABC-1234: null
com.atlassian.fisheye.jira.RemoteJiraException: Unknown error creating subtask for issue ABC-1234: null
	at com.atlassian.fisheye.jira.JiraIssueImpl.createSubtask(JiraIssueImpl.java:231)
	at com.cenqua.crucible.actions.jira.LinkCommentIssueAjaxAction.createSubtaskForComment(LinkCommentIssueAjaxAction.java:114)
	at com.cenqua.crucible.actions.jira.LinkCommentIssueAjaxAction.execute(LinkCommentIssueAjaxAction.java:70)	
2011-09-12 18:28:01,395 DEBUG [btpool0-583 ] fisheye.app BaseCommentIssueAjaxAction-error - Error creating subtask in JIRA: Unknown error creating subtask for issue ABC-1234: null
2011-04-12 18:28:01,395 DEBUG [btpool0-583 ] fisheye.perf ProfilingServletFilter-logRequest - end request POST /json/cru/ABC-1234/linkCommentIssueAjax/?summary=Yes%20here%20tool&assignee=-1&commentId=66 sessionid=j6ywby4ksy6ftbeur8f1o5rr

原因

How To Resolve

The user logged in Crucible may not exist in JIRA, or does not have permissions to create issues in that JIRA project.Make sure that the user logged in Crucible also exists in JIRA and has permissions to create issues in that JIRA project, by checking the JIRA project's permission schemes.
The JIRA projects "default assignee" is unassignable. This is only a possible issue in instances where the assignee is set to "-Automatic-".Make sure that the "default assignee" has Assignable User (Users with this permission may be assigned to issues) permission as: User, Group, or Project Role
The Crucible review the user is trying to create JIRA issues from may not have a JIRA issue linked to it.Make sure that the Crucible review the user is trying to create JIRA issues from has a JIRA issue linked to it.
This error can also happen if a 'Closed' JIRA ticket is linked to the Crucible review the user is trying to create JIRA sub-tasks from. This is impossible yet: CRUC-3956 - Getting issue details... STATUS

Make sure to link an 'Open' JIRA ticket to the Crucible review.

This error can also happen if the JIRA issue has mandatory custom fields that must be filled at the moment of issue creation. As Crucible is not aware of these JIRA custom fields, this can be causing the error. This bug was already reported:  CRUC-2667 - Getting issue details... STATUS Make sure that the JIRA issue does not have mandatory custom fields that must be filled at the moment of issue creation.

Sometimes both JIRA and Fisheye need to be restarted in order to apply the changes.

The JIRA project you link to doesn't know about the sub-task issue type you configured in the Application Link.Make sure the sub-task issue types can be created in the JIRA Project. This can be done by adding the sub-task issue type to the Issue Type Schema

診断

  1. Turn on the HTTP dump log in JIRA (Administration > Logging & Profiling):
    1. Enable the HTTP access log.
    2. Enable the HTTP dump log.
  2. Attempt to create another subtask from Crucible.
  3. Inspect the <JIRA home directory>/log/atlassian-jira-http-dump.log file and look for more information after the following HTML snippet:

    <div class="aui-message error"><span class="aui-icon icon-error"></span>
最終更新日 2018 年 7 月 31 日

この内容はお役に立ちましたか?

はい
いいえ
この記事についてのフィードバックを送信する
Powered by Confluence and Scroll Viewport.