Sprint issues and project lead are inconsistent across different users and browsers

Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. 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.

*Except Fisheye and Crucible

Summary

Users are seeing different project leads and issues in the same agile sprint and project, even after clearing the browser cache and reindexing the instance. 

Diagnosis

1 content: 'Project Lead'}) + JIRA.Templates.Fields.Pickers.User.single({field: opt_data.field, options: opt_data.options, editValue: opt_data.value})

Cause

The environment is configured with an incompatible scripted custom field user picker.

Solution

  1. Update the scripted custom field or remove it from the project. 

  2. Temporarily remove any custom html, css, or javascript which can be found in the database:

1 2 3 4 5 select * from customfield where description like '%script%' or description like '%html%' or description like '%css%' or description like '%<script%' or description like '%<SCRIPT%'; select * from fieldconfiguration where description like '%avascript%' or description like '%html%' or description like '%css%' or description like '%<script%'; select * from fieldconfigscheme where description like '%<script%' OR description like '%<SCRIPT%'; select * from fieldlayoutitem where description like '%avascript%' or description like '%html%' or description like '%css%' or description like '%<script%'; select * from propertytext where id in (select id from propertyentry where property_key='jira.alertheader');

Updated on February 24, 2025

Still need help?

The Atlassian Community is here for you.