Issue Summary

This is reproducible on Data Center: (yes)

Steps to Reproduce

1. Create a new Plan
   • Give it a name
   • Choose the Access type
   • Select a Board as the Issue source
2.  Go to JIRA Administration (⚙︎) > System > SHARED ITEMS > Filters
   • Delete the filter that belongs to the Board configured as an Issue source in the Plan
3. Go to Plans > Plan > (⚙︎) > Configure > Issue sources

Expected Results

Being able to choose a different Issue source:

Actual Results

A spinning wheel is shown:

The below exception is thrown in the atlassian-jira.log file:

ERROR - - SESSION IP /rest/jpo/1.0/plans/*PLAN_ID*/basicinfo [c.a.r.c.r.provider.exception.DefaultExceptionMapper] com.atlassian.rm.common.bridges.agile.AgileServiceOutcomeException: 
Could not get filter for board ID: *BOARD_ID*
tlassian.rm.common.env.EnvironmentServiceException: com.atlassian.rm.common.bridges.agile.AgileServiceOutcomeException: Could not get filter for board ID: *BOARD_ID*

.
.
.
Caused by: com.atlassian.rm.common.bridges.agile.AgileServiceOutcomeException: Could not get filter for board ID: BOARD_ID

Diagnosis

The SQL queries were written and tested on PostgreSQL and might need to be amended if Jira is using a different type of database

• Retrieve all the Issue sources associated with the affected plan. Change <PLAN_ID> for the affected Plan ID.

  SELECT plan."ID", plan."TITLE" as "Plan Name", plansrc."SOURCE_TYPE" as "Source Type", plansrc."SOURCE_VALUE" as "Source ID"
  FROM "AO_D9132D_ISSUE_SOURCE" plansrc, "AO_D9132D_PLAN" plan
  WHERE plansrc."PLAN_ID" = plan."ID" and plan."ID" = <PLAN_ID>;
  

• Retrieve the Filter associated with a Board. A board needs one filter to work properly, otherwise, we might be having a broken Board assigned to a Plan causing this problem. Change <BOARD_ID> for the affected Board ID shown in the log files.

  SELECT board."ID" as "Board ID", board."NAME" as "Board Name", board."OWNER_USER_NAME" as "Board Owner", filter.filtername as "Filter name", filter.authorname as "Filter Owner", filter.reqcontent as "Filter Query"
  FROM "AO_60DB71_RAPIDVIEW" board, searchrequest filter
  WHERE filter.id = board."SAVED_FILTER_ID" and board."ID" = <BOARD_ID>
  

  • In case you have more than one Board configured as an Issue source:

    SELECT board."ID" as "Board ID", board."NAME" as "Board Name", board."OWNER_USER_NAME" as "Board Owner", filter.filtername as "Filter name", filter.id as "Filter ID", filter.authorname as "Filter Owner", filter.reqcontent as "Filter Query"
    FROM "AO_60DB71_RAPIDVIEW" board, searchrequest filter
    WHERE filter.id = board."SAVED_FILTER_ID" and board."ID" in (<BOARD_ID>, <BOARD_ID>,...)
    

    • If the query is not returning any Filter, it means that a broken Board is assigned to the Plan and this is causing the problematic behavior.

Workaround

To this point, we know if one or more Boards are causing problems and their Board ID. Let's proceed to remove any faulty Board from the Plan Issue sources.

1. Stop Jira - changes won't take effect if we don't take down the Jira instance.
2. Run the following SQL query to remove the faulty Board(s) from the Plan Issue sources:
   • The SQL query was written and tested on PostgreSQL, and might need to be amended if Jira is using a different type of database
     • Replace <PLAN_ID> with your actual plan ID
     • Replace <BOARD_ID> with the detected faulty Board Board ID, in case you have more than one faulty Board, add as many Board IDs as you need i.e.: (cast(<BOARD_ID> as varchar), cast(<BOARD_ID> as varchar), ...)

       delete from "AO_D9132D_ISSUE_SOURCE" ais where ais."PLAN_ID"= <PLAN_ID> and ais."SOURCE_TYPE"='Board' and ais."SOURCE_VALUE" in (cast(<BOARD_ID> as varchar))
       

3. Start Jira and verify if you can access the Plan