Issue source of type Board, with value [board_id] could not be found

お困りですか?

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

コミュニティに質問

プラットフォームについて: Server および Data Center のみ。この記事は、Server および Data Center プラットフォームのアトラシアン製品にのみ適用されます。

Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Fisheye および Crucible は除く

要約

Check what to do when your Jira Cloud Migration Assistant (JCMA) migration fails with "We couldn't import Issue Source <issue-source-id>. Reason: Issue source of type Board, with value [board_id] could not be found".

概要

This error occurs when the migration user can't access the mentioned board on the cloud. The board_id refers to the board present on the cloud.

ERROR CROSS-PROJECT-DATA project-import We couldn't import Issue Source <issue-source-id>. Reason: Issue source of type Board, with value [board_id] could not be found.

検証

Validate if the migration user has access to the cloud board. One can use the URL below to validate that.

Replace the <board_id> placeholder with the one from the log message and the <instance> with the cloud site name.

https://<instance>.atlassian.net/secure/RapidBoard.jspa?rapidView=<board_id>

エラー ログ:

ERROR CROSS-PROJECT-DATA project-import We couldn't import Issue Source 1. Reason: Issue source of type Board, with value [123] could not be found.

URL: https://mysitename.atlassian.net/secure/RapidBoard.jspa?rapidView=123

ユーザーがアクセス権を持っていない場合は、次のポップアップが表示されます。

The error when the user can't access the board

ソリューション

ボードにアクセスするには、移行を実行しているユーザーに次の権限が必要です。

  1. Permission to see the filter associated with the board.
  2. Permission to browse the project where the board is located.

To identify which groups or project roles the user must have to see the filter, the user can verify this on the on-prem instance.

フィルターの表示権限

データベース経由

Identify the permissions associated with the filter that have a relationship with the board within the plan. Replace the <issue-source-id> with the one present on the error logs.

PostgresSQL
SELECT r."NAME"      AS board_name 
	 , sr.filtername AS filter_name
	 , sr.reqcontent AS JQL
     , sp.sharetype  AS share_type
	 , CASE WHEN sp.sharetype = 'project' THEN p.pkey ELSE sp.param1 END AS param
  FROM "AO_D9132D_ISSUE_SOURCE" s
  JOIN "AO_60DB71_RAPIDVIEW" r ON (r."ID" = s."SOURCE_VALUE"::int)
  JOIN searchrequest sr        ON (sr.id = r."SAVED_FILTER_ID")
  JOIN sharepermissions sp     ON (sp.entityid = r."SAVED_FILTER_ID")
  LEFT JOIN project p          ON (p.id::text = sp.param1 AND sp.sharetype = 'project')
  WHERE s."SOURCE_TYPE" = 'Board'
    AND s."ID" = <issue-source-id>
    AND sp.entitytype = 'SearchRequest';
Oracle
SELECT r.NAME        AS board_name 
	 , sr.filtername AS filter_name
	 , sr.reqcontent AS JQL
     , sp.sharetype  AS share_type
	 , CASE WHEN sp.sharetype = 'project' THEN p.pkey ELSE sp.param1 END AS param
  FROM AO_D9132D_ISSUE_SOURCE s
  JOIN AO_60DB71_RAPIDVIEW r ON (dbms_lob.compare(s.SOURCE_VALUE, TO_CLOB(r.ID)) = 0)
  JOIN searchrequest sr      ON (sr.id = r.SAVED_FILTER_ID)
  JOIN sharepermissions sp   ON (sp.entityid = r.SAVED_FILTER_ID)
  LEFT JOIN project p        ON (sp.param1 = TO_CHAR(p.id) AND sp.sharetype = 'project')
 WHERE s.SOURCE_TYPE = 'Board'
   AND s.ID = <issue-source-id>
   AND sp.entitytype = 'SearchRequest';
MySQL
SELECT r.NAME        AS board_name 
	 , sr.filtername AS filter_name
	 , sr.reqcontent AS JQL
     , sp.sharetype  AS share_type
	 , CASE WHEN sp.sharetype = 'project' THEN p.pkey ELSE sp.param1 END AS param
  FROM AO_D9132D_ISSUE_SOURCE s
  JOIN AO_60DB71_RAPIDVIEW r ON (CAST(s.SOURCE_VALUE AS UNSIGNED) = r.ID)
  JOIN searchrequest sr      ON (sr.id = r.SAVED_FILTER_ID)
  JOIN sharepermissions sp   ON (sp.entityid = r.SAVED_FILTER_ID)
  LEFT JOIN project p        ON (sp.param1 = CAST(p.id AS CHAR) AND sp.sharetype = 'project')
 WHERE s.SOURCE_TYPE = 'Board'
   AND s.ID = <issue-source-id>
   AND sp.entitytype = 'SearchRequest';
MSSQL Server
SELECT r.NAME        AS board_name 
	 , sr.filtername AS filter_name
	 , sr.reqcontent AS JQL
     , sp.sharetype  AS share_type
	 , CASE WHEN sp.sharetype = 'project' THEN p.pkey ELSE sp.param1 END AS param
  FROM AO_D9132D_ISSUE_SOURCE s
  JOIN AO_60DB71_RAPIDVIEW r ON (CAST(s.SOURCE_VALUE AS NUMERIC) = r.ID)
  JOIN searchrequest sr      ON (sr.id = r.SAVED_FILTER_ID)
  JOIN sharepermissions sp   ON (sp.entityid = r.SAVED_FILTER_ID)
  LEFT JOIN project p        ON (sp.param1 = CAST(p.id AS VARCHAR(MAX)) AND sp.sharetype = 'project')
 WHERE s.SOURCE_TYPE = 'Board'
   AND s.ID = <issue-source-id>
   AND sp.entitytype = 'SearchRequest'

Based on the query results, mirror the same permissions on the cloud side.

board_namefilter_nameJQLshare_typeparam
CLAUD boardFilter for CLAUD boardproject = CLAUD ORDER BY Rank ASCgroupjira-administrators
CLAUD boardFilter for CLAUD boardproject = CLAUD ORDER BY Rank ASCプロジェクトCLAUD

For this case, add the user to the jira-administrators group and have "Browse Projects" for the project CLAUD.

UI 経由

  1. Access the board.
  2. Click on the Configure option on the board dropdown.
  3. Go to the General option.
  4. Look for the Shares configuration.
  5. Adjust the cloud permissions to reflect the same ones listed on the on-prem site.

プロジェクトの参照

You might need to use the database query above to determine which project the board may be related to on the cloud.

  1. Access the project settings that will host the board on the cloud.
  2. Go to the permission scheme.
  3. Look for the groups/users/projects roles associated with the "Browse Projects" permission.
  4. Adjust the cloud permissions to reflect the same ones listed on the on-prem site.



最終更新日 2024 年 4 月 18 日

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

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